Created capabilities (commands): gsd-discuss-phase, gsd-plan-phase, gsd-execute-phase, gsd-verify-work, gsd-ship
Created capabilities (sub-agents): gsd-phase-researcher, gsd-planner, gsd-plan-checker, gsd-executor, gsd-verifier
Created sdlc-stage projections: stage-discuss, stage-plan, stage-execute, stage-verify, stage-ship
Created artifacts: artifact-context-md, artifact-plan-md, artifact-research-md, artifact-uat-md, artifact-atomic-commit, artifact-pull-request
Created patterns: pattern-spec-driven-development, pattern-fresh-context-subagents, pattern-wave-parallelism, pattern-plan-verification-loop
Conflict recorded: docs homepage “Research→…” vs README/detailed pages “Discuss→…” (canonical: Discuss) — noted in gsd.md and stage-discuss.md
Scope note: documented the 5 workflow commands + 5 core sub-agents; remaining 60+ commands and 29 sub-agents catalogued in gsd.md for future ingest
[2026-06-27] edit | bullet-list formatting for capability enumerations
CONVENTIONS.md: added “Formatting conventions” — enumerate commands/sub-agents as one-per-line bullets ([[link]] — role note), grouped under sub-headings for long rosters
gsd.md: converted Commands, namespaces, Sub-agents (documented + not-yet-documented, now grouped by function), Artifacts, Patterns from inline ·/prose runs to bullet lists
Pattern pages: expanded “Applied by” single-bullet runs into per-capability bullets
Artifact pages: expanded “Produced by” runs into per-capability bullets
[2026-06-28] ingest | Matt Pocock — Skills for Real Engineers (mattpocock/skills)
Conflict recorded: CONTEXT.md filename means different artifacts in GSD (locked decisions) vs MP (domain glossary) — annotated in both artifact-context-md and artifact-domain-model
Cascade: updated all implements: edges, prose, See Also, and index paths across ~25 pages; added aka: to all 5 stage pages; bumped stage updated: to 2026-07-01
Note: historical log entries above retain the old stage names (they record what the stages were called at the time)
[2026-07-01] edit | capture split candidates on stage-plan
stage-plan.md: added ”## Split candidates” section tracking stage-specify (spec/PRD authoring) and stage-design (deep-module design); each with distinction, evidence tally (1 strong vote each — MP splits, GSD folds in), and decisive trigger (spec-first framework e.g. SpecKit/OpenSpec → stage-specify; third design-distinct framework → stage-design)
CONVENTIONS.md: added “Park pending splits on the stage page” rule — split candidates live under a ## Split candidates heading as the per-ingest review queue
No renames/new stages yet — evidence still below the ≥2-framework threshold
STAGE RE-DERIVATION (third framework in evidence):
PROMOTED stage-specify (author the spec/PRD, distinct from task decomposition): Addy’s spec-driven-development became the 2nd framework (with MP’s to-prd) to treat spec authoring as its own step → cleared the ≥2-framework bar. Split out of stage-plan; moved mp-to-prd’s implements stage-plan → stage-specify; wired addy-spec-driven-development. aka: { matt-pocock-skills: to-prd, addy-agent-skills: spec-driven-development }
PARKED stage-review (quality gate: is it good?) as the strongest split candidate on stage-validate: Addy cleanly separates Verify (does it work) from Review (is it good), but is the only framework treating them as distinct phases (MP contributes only review-side, GSD only functional-side) — below the ≥2 bar. Decisive trigger noted: a second framework separating quality review as its own phase (likely Superpowers).
stage-design candidate refreshed: Addy adds a dedicated design skill (addy-api-design) but folds it into Build → design is now a dedicated capability in 2 frameworks but a distinct phase in only 1 (MP); still parked.
stage-release parked a watch-item (operate/maintain) for Addy’s observability + deprecation folded into Ship.
Scope: documented all 24 skills + 4 personas as capability pages (full coverage). The 8 slash commands are thin skill-invokers, catalogued as a phase↔command↔skill↔stage table on the framework page rather than given separate pages; 7 reference checklists + hooks catalogued on the framework page.
Noted for a future ingest: Superpowers (obra) — referenced in Addy’s docs/comparison.md; likely trigger for promoting stage-review.
[2026-07-04] ingest | OpenSpec — spec-driven development (Fission-AI/OpenSpec)
added reciprocal equivalent_to edges on all 10 counterpart capability pages + a reciprocal See Also bullet on each
STAGE RE-DERIVATION (fourth framework in evidence — no renames/splits/merges/adds this ingest):
stage-specify reinforced to three frameworks: openspec-propose centers on authoring the spec (as spec deltas) before code, joining MP + Addy. Stage now beyond doubt.
stage-align now four-framework: added openspec-explore. Noted a second flavor — codebase-investigation (OpenSpec/Addy idea-refine) alongside human-interrogation (grilling cluster). One framework only for explicit codebase-explore → no split.
stage-plan: OpenSpec folds plan into propose (design.md + tasks.md); its implements edge points at stage-specify. stage-design split candidate refreshed — OpenSpec adds a dedicated design.md artifact as a discrete step in proposal→specs→design→tasks, so design is now a dedicated capability/artifact in 3 frameworks but a distinct phase in only 1 (MP); still parked.
stage-validate: openspec-verify added on the functional/spec-conformance side only (OpenSpec ships no quality review) → does NOT advance the parked stage-review split (still Addy-only as distinct phases).
stage-release: added openspec-sync + openspec-archive. Recorded two flavors of release — ship-to-prod (GSD/Addy) vs spec-maintenance (OpenSpec: merge delta into living spec, no deploy/CI/observability). Addy’s ops capabilities still unique.
Cascade (updated + dates 2026-07-04): pattern-spec-driven-development (OpenSpec applied-by + living-spec note); artifact-plan-md (OpenSpec tasks.md producer); artifact-adr (design-md See Also); all 6 stage pages (backlinks, aka, equivalents, split-candidate refresh); 10 counterpart capabilities (reciprocal equivalent_to + See Also); framework See Also cross-links on gsd, addy-agent-skills, matt-pocock-skills
Scope: paged the 6 core workflow commands (explore/propose/apply/verify/sync/archive). Expanded-profile commands (new, continue, ff, bulk-archive, onboard) are thin artifact-generation/batch/tutorial wrappers → catalogued as a table on the framework page (per full-coverage-but-catalogue-thin-wrappers convention). Terminal CLI (init/update/config/validate/list/show/diff/archive) catalogued as a tooling table, not lifecycle capabilities. Legacy /openspec: commands noted as deprecated.
[2026-07-04] ingest | Spec Kit — spec-driven development (github/spec-kit)
Created framework: speckit (fifth framework; GitHub’s reference implementation of SDD — Spec→Plan→Tasks→Implement; largest community, 106K★)
Created capabilities (commands, 10 — full per-command coverage per user preference): speckit-constitution, speckit-specify, speckit-clarify, speckit-plan, speckit-tasks, speckit-analyze, speckit-implement, speckit-checklist, speckit-converge, speckit-taskstoissues
Created artifacts (2): artifact-constitution (signature — immutable project-wide governing principles in numbered articles, .specify/memory/constitution.md), artifact-checklist (“unit tests for your English” — requirements quality gate). Reused artifact-spec-md (spec.md), artifact-design-md (plan.md/data-model.md/contracts), artifact-research-md (research.md), artifact-plan-md (tasks.md), artifact-issue (taskstoissues).
Created patterns (1): pattern-project-constitution (externalize immutable principles into one governing doc + gate every artifact against it — SpecKit’s distinctive contribution)
added reciprocal equivalent_to edges + See Also bullets on all counterpart capability pages
Pattern promotions from single- to two-framework: pattern-contract-first (Addy + SpecKit contracts/), pattern-plan-verification-loop (GSD + SpecKit). pattern-spec-driven-development, pattern-test-driven-development, pattern-grilling extended with SpecKit.
STAGE RE-DERIVATION (fifth framework in evidence — no renames/merges this ingest):
stage-specify reinforced to four frameworks: speckit-specify is the literal /specify step. SpecKit adds a distinctive spec-quality gate (speckit-checklist → artifact-checklist).
stage-align now five-framework: added speckit-clarify (grilling, spec-first ordering variant). PARKED stage-govern split candidate: speckit-constitution establishes project-wide governing principles gated across artifacts — a genuine governance activity, but SpecKit is the only framework with it (others embed principles inside skills; OpenSpec has none). Below the ≥2 bar. Decisive trigger: a second framework with a set-the-project-principles capability.
stage-plan: added speckit-plan + speckit-tasks + speckit-analyze + speckit-taskstoissues. Plan-verification cluster promoted to two-framework (gsd-plan-checker ↔ speckit-analyze). stage-design candidate refreshed — SpecKit emits dedicated design artifacts (data-model.md + contracts/) within plan → design now a dedicated capability/artifact in 4 frameworks but a distinct phase in only 1 (MP); still parked.
stage-implement: added speckit-implement (strictest test-first — TDD mandated by the constitution).
stage-validate: added speckit-converge on the functional/spec-conformance side (action-oriented — re-plans the gap into new tasks rather than only reporting). SpecKit ships no quality-gate review → does NOT advance the parked stage-review split (still Addy-only as distinct phases).
stage-release: SpecKit adds NO backlink — it stops at the validate loop; no deploy/PR/launch/observability command. Noted on the stage page.
Scope: paged all 10 slash commands (5 core + 5 optional) for full per-command coverage. The Specify CLI (init/self/integration/extension/preset/bundle) catalogued as a tooling table on the framework page, not lifecycle capabilities. Noted source discrepancy on speckit-checklist (current docs = requirements-quality; older spec-driven.md = code-vs-spec) — followed current docs.
Housekeeping: removed stray </content> tags left in pattern-contract-first.md and artifact-spec-md.md while editing them.
Created framework: bmad (sixth framework; the most role-oriented & lifecycle-complete — six named personas over Analysis→Planning→Solutioning→Implementation, scale-adaptive, context-engineered)
Created capabilities — sub-agent personas (6): bmad-analyst (Mary), bmad-tech-writer (Paige), bmad-pm (John), bmad-ux-designer (Sally), bmad-architect (Winston), bmad-dev (Amelia)
Created patterns (2): pattern-persona-agents (signature — named expert persona per role + Party Mode), pattern-scale-adaptive-planning (signature — size ceremony to work; Levels 0-4 / Quick-Method-Enterprise tracks; JIT design)
Cross-framework synthesis (six-framework payoff):
specify cluster → FIVE-framework: bmad-prd ↔ mp-to-prd / addy-spec-driven-development / openspec-propose / speckit-specify (reciprocal equivalent_to + See Also on all four)
STAGE RE-DERIVATION (sixth framework — no renames/splits/merges/adds; all candidates refreshed):
stage-align → six-framework. BMAD is the first to populate all three align flavors at once (grilling via facilitator personas, codebase-investigation via document-project, ideation via brainstorming) + adds an adversarial pressure-testing sub-flavor (forge-idea, prfaq). stage-govern NOT advanced — BMAD’s project-context.md/customize.toml are dev rules, not an immutable charter; still SpecKit-only.
stage-specify → five-framework (bmad-prd); BMAD reinforces structurally by giving specify its own Planning phase between Analysis and Solutioning.
stage-plan: added bmad-architect/architecture/create-epics-and-stories/check-implementation-readiness/sprint-planning/create-story/correct-course. stage-design candidate refreshed — BMAD has a dedicated architecture capability + a named Solutioning phase, but Solutioning bundles design+decomposition, so it does NOT isolate design from decomposition as a distinct phase; design now a dedicated capability in FIVE frameworks, distinct phase in only one (MP). Still parked.
stage-implement → six-framework execute cluster (bmad-dev-story + bmad-quick-dev); create-story noted as the plan→implement bridge.
stage-validate: added bmad-code-review (adversarial). stage-review split NOT advanced — BMAD ships a genuine quality-gate (code-review + optional TEA module) cleanly separated from functional testing, but inside the Implementation loop, not as a distinct phase; review now a dedicated capability in ~3 frameworks but a distinct phase in only one (Addy).
stage-release: added bmad-retrospective — a THIRD flavor of release (“learning close-out”), alongside ship-to-prod (GSD/Addy) and spec-maintenance (OpenSpec). BMAD core, like SpecKit, ships no deploy step — but unlike SpecKit it DOES add a close-out backlink. Cluster left as non-equivalent (terminal acts differ too much).
Scope: paged the 6 BMM personas + 19 lifecycle workflow skills (full per-capability coverage per user preference). Cross-phase utility skills (party-mode, advanced-elicitation, review layers, checkpoint-preview, sprint-status, generate-project-context, qa-generate-e2e-tests, dev-auto, shard-doc, help/customize/index-docs) catalogued as a table on the framework page. Optional modules (BMB, CIS, TEA, GDS, WDS, BMad Loop) catalogued as a table, not paged (like GSD’s Pi/Browser and OpenSpec’s expanded profile) — TEA’s Murat noted as BMAD’s quality-reviewer, clustering with stage-validate.
Conflict recorded (version drift): v4/v5 shipped separate Scrum Master (Bob) / Product Owner (Sarah) / BMad Master / BMad Orchestrator agents; v6 folds SM+QA into the Developer (Amelia), epic breakdown into the PM (John), orchestration into the party-mode skill. Some secondary sources (DeepWiki) still list a sm/”Bob” agent; v6 docs canonical at “six named agents.” Annotated on bmad.md.
Version note: v6 migrated to a Claude-Code Agent-Skills architecture (SKILL.md) and replaced the classic numeric Levels 0-4 with stakes-calibrated tracks (Quick Flow / BMad Method / Enterprise); both representations documented on pattern-scale-adaptive-planning.
Housekeeping: removed stray </content> tags found in pattern-parallel-persona-review.md, pattern-adversarial-review.md, pattern-context-engineering.md, artifact-review-report.md, and framework/addy-agent-skills.md while cascading.
Raw: raw/compound-engineering/2026-07-04-compound-engineering-every.md (every.to essay, Shipper & Klaassen, 2025-12-11) + 2026-07-04-compound-engineering-plugin.md (GitHub README + docs/skills + repo tree via gh api)
Created framework: compound-engineering (seventh framework; the only self-feeding loop — Brainstorm→Plan→Work→Simplify→Review→Compound + autonomous /lfg; 80/20 planning-review split; knowledge compounding to docs/solutions/)
NEW CANONICAL STAGE — stage-learn (the headline). User asked whether the “compound” step is a new SDLC stage. Answer per the re-derivation rules: yes. Learning-capture was already latent as the “learning close-out” flavor of stage-release (bmad-retrospective, single-framework, parked). CE’s ce-compound (+ ce-compound-refresh, ce-explain) gives it a second framework, clearing the ≥2-framework bar — same mechanism that promoted stage-specify out of stage-plan.
STAGE SPLIT (stage-release → stage-learn): moved bmad-retrospective implements: stage-release → stage-learn (+ applies pattern-knowledge-compounding); rewrote bmad-retrospective body + See Also. Created sdlc-stage/stage-learn.md (definition, why-distinct-not-a-flavor, two flavors: agent-grounding corpus vs team retrospective, spec-flavored cousin = openspec-sync). Edited stage-release: aka (dropped bmad, added compound-engineering), “three flavors”→“two flavors” note + promotion note, added CE ship-to-prod backlinks (ce-commit/commit-push-pr/resolve-pr-feedback/promote/product-pulse), rewrote cross-framework equivalents + See Also. This is the wiki’s 7th canonical stage and arguably the first genuinely new stage the agent era adds (machine-consumable learnings, not a rename of a classic phase).
learn cluster (new): ce-compound ↔ bmad-retrospective (left non-equivalent — differing terminal acts, like the release cluster)
added reciprocal equivalent_to edges on all counterpart capability pages (30 edits)
STAGE RE-DERIVATION (seventh framework):
stage-learn PROMOTED (see above).
stage-align → seven-framework (ce-brainstorm/ideate/pov/strategy/sweep); added CE ideation + a new evaluate-external-inputs sub-flavor (ce-pov). stage-govern NOT advanced — CE’s STRATEGY.md is a product-strategy context anchor, not an immutable gated charter; still SpecKit-only.
stage-plan → seven-framework; plan-verification promoted to FOUR frameworks (ce-doc-review, persona-fan-out variant). design candidate unchanged.
stage-validate: stage-review split strengthened but NOT promoted — CE makes Simplify (4) + Review (5) explicit distinct loop phases (closer to Addy than BMAD), so review-as-a-distinct-phase now appears in TWO frameworks (Addy, CE); but CE lacks a co-equal functional-validation phase (testing skills are on-demand), so the clean Verify∥Review partition is still cleanest in Addy alone. Not promoted — also avoids two stage-splits in one ingest (minimize rule). Decisive trigger refreshed.
stage-release: two flavors now (learning close-out moved out).
Scope: paged all 26 lifecycle skills + lfg (full per-capability coverage per user preference). The 26 shared sub-agents (research/grounding, review specialists, design/planning) + ~23 review-persona lenses are catalogued grouped-by-function on the framework page rather than individually paged (per the catalogue-thin-helpers convention, as with GSD’s sub-agent roster) — noted here for a future ingest if per-sub-agent pages are wanted. Infra/product-specific skills ce-setup, ce-proof (Proof editor), ce-riffrec-feedback-analysis (Riffrec) catalogued on the framework page, not paged.
User directed full per-sub-agent coverage (reinforces the standing full-coverage memory, which already covers sub-agents). Reversed the prior “catalogue-only” scoping for the 26 CE sub-agents.
Created 26 sub-agent capability pages (subtype: sub-agent, ce--prefixed per the framework-prefixed unique-basename convention), each filed by intrinsic activity:
Note: the compound-council reviewers (security/performance/pattern/data-integrity) are filed by intrinsic activity (validate) with their ce-compound learning role noted, since that’s where their cross-framework counterparts live; the pure researchers/historians file under learn.
Descriptions sourced from the actual agent definitions (gh api on skills//references/agents/.md).
New cross-framework equivalent_to (reciprocal both ways): ce-security-sentinel ↔ addy-security-auditor; ce-performance-oracle ↔ addy-web-performance-auditor.
Wiring: delegates_to populated on 11 dispatching skills (ce-brainstorm/ideate/pov/plan/work/optimize/sweep/resolve-pr-feedback/compound/explain/code-review) → their sub-agents; framework page sub-agent roster rewritten from code-name catalogue to grouped wikilink list (“each paged”); produced-by backlinks added on artifact-security-audit (+ce-security-sentinel), artifact-perf-audit (+ce-performance-oracle), artifact-launch-checklist (+ce-deployment-verification-agent), artifact-explainer (+ce-work-recap-scout), artifact-solution-doc (+7-member council); applied-by bullets added on patterns fresh-context-subagents, source-grounding, knowledge-compounding, adversarial-review, measure-first, plan-verification-loop, context-engineering, deep-modules; index.md +26 sub-agent rows; framework updated → 2026-07-05.
Retained catalogue-only (non-lifecycle): ~23 review-persona lenses inside ce-code-review/ce-doc-review (bundled reference lenses, not standalone agents), and infra/product skills ce-setup/ce-proof/ce-riffrec-feedback-analysis.
[2026-07-05] ingest | gstack (Garry Tan / YC) — eighth framework, largest here
Framework page framework/gstack.md created. Sprint: Think→Plan→Build→Review→Test→Ship→Reflect. The largest framework in the wiki (~54 skills). Ethos: Boil the Ocean / Search Before Building / User Sovereignty.
CAPABILITIES: 54 pages created (full per-capability coverage per standing memory) — all 53 SKILL.md skills + the root router (gstack-router; equivalent_to addy-using-agent-skills). All subtype: command (gstack ships slash-command skills; role personas rather than separately-paged sub-agents). Filed by sprint stage:
stage-learn → THREE frameworks (beyond doubt). gstack ships BOTH flavors — team retrospective (gstack-retro → artifact-retrospective) + agent-grounding corpus (gstack-learn → artifact-solution-doc) + capability-compounding (gstack-skillify). First framework to populate both flavors at once.
stage-validate: stage-review split BAR NOW CLEARED (⚑ not yet executed). gstack is the SECOND framework (after Addy) with a clean Review phase ∥ Test phase partition — the exact decisive trigger. Marked cleared on the stage page + index with a recommendation to promote (stage-validate functional + stage-review quality gate) as a focused next pass — deferred because it’s a ~17-capability re-pointing cascade across the existing wiki that merits its own verifiable ingest, not bundling into gstack’s (already large) one.
stage-release: stage-operate candidate strengthened to capability-level in THREE frameworks (Addy + CE + gstack). gstack is the first with a genuine deploy command (land-and-deploy) separate from ship + a post-deploy monitor (canary), but still nests them under release rather than a standalone Operate phase — so strengthened, not promoted.
Executed the follow-up flagged above. Promoted stage-review as the 8th canonical stage, splitting the (previously widest) stage-validate into its two long-parked halves once gstack became the 2nd framework (after Addy) with a clean Verify (functional) ∥ Review (quality) phase partition — clearing the ≥2-framework bar (same mechanism as stage-specify ← stage-plan and stage-learn ← stage-release).
Frameworks: MP, Addy, BMAD, CE, gstack (5). GSD, OpenSpec, and Spec Kit ship no review capability (functional validators only) — the clean absence that made the split correct.
Classification rule (framework-neutral, by activity): run it and observe → validate; read it and judge quality → review. equivalent_to clusters kept intact within one stage (code-review, security, performance, simplification, browser-testing, iOS-test). Judgment calls: gstack-benchmark → review (performance cluster, not “Test” despite gstack’s label); addy-test-engineer → review (Addy’s Review-phase /ship persona); gsd-verifier → validate (goal-backward = functional).
New page: sdlc-stage/stage-review.md (full projection: promoted-note, why-distinct, backlinks by framework, clusters, See Also). Rewrote sdlc-stage/stage-validate.md to functional-only (removed the review backlinks, narrowed the definition/aka, replaced the split-candidate section with a “resolved” note).
Stage count now 8: align · specify · plan · implement · validate · review · release · learn.
Dangling-wikilink check: to be confirmed clean post-cascade.
[2026-07-09] ingest (update) | Matt Pocock — Skills for Real Engineers v1.1
Re-ingest of github.com/mattpocock/skills at v1.1 (was 2026-06-28). New raw: raw/matt-pocock-skills/2026-07-09-skills-v1.1-update.md (README + full SKILL.md catalogue across engineering/productivity/misc/deprecated/in-progress/personal + CHANGELOG v1.1 highlights). Old raw retained (immutable).
RENAMES (page + full wikilink cascade across 20 files; log.md history left intact):
to-prd → mp-to-spec — “spec” is now the through-line term; produces artifact-spec-md, no longer artifact-prd (still opens “you may know this as a PRD”).
to-issues + to-plan → mp-to-tickets (to-issues deleted) — tracer-bullet tickets with blocking edges; local tickets.md vs native tracker links; wide-refactor expand–contract.
Source: github.com/buildermethods/bm-skills (Brian Casel). A Claude Code plugin marketplace of small, independent builder utilities — not a full-SDLC framework; ingested primarily to capture the PRD Creator. Raw: raw/bm-skills/2026-07-09-bm-skills.md (README + CLAUDE + 3 SKILL.md + PRD step catalogue).
Framework page framework/bm-skills.md (noted explicitly as a light utility collection, not a lifecycle engine).
Source: github.com/tao-hpu/nano-spec (Tao An, MIT, 46★) + intro article “The Sweet Spot Between Chaos and Over-Engineering in AI-Assisted Development” (Generative AI / Medium, 2025-12-01). Raw: raw/nano-spec/2025-12-01-nano-spec.md (README + SKILL.md verbatim + article digest). A deliberately minimal, tool-agnostic spec methodology — “Spec-driven thinking, nano-sized docs”; not a full-SDLC framework (like bm-skills).
Framework page framework/nano-spec.md carries the requested source_url (repo) and docs_url (article) frontmatter properties in addition to the standard sources:/raw:.
CAPABILITIES (3 paged, full coverage per the one-page-per-action convention; one /nano-spec skill, $ACTION = create/status/update, re-published as system-prompt configs for 9 other agents): nano-spec-create (focus — specify; generates the 4-doc pack), nano-spec-status (no stage — read-only progress report; session-handoff), nano-spec-update (no stage — living-doc maintenance; session-handoff).
NEW artifact artifact-nano-spec-pack (nano-spec’s signature: tasks/{name}/ README+todo+doc+log). Component mappings also wired to existing artifacts: artifact-plan-md (+nano-spec todo.md), artifact-adr (+nano-spec doc.md Key Decisions).
PATTERNS: pattern-spec-driven-development (+nano-spec, minimalist instance; also back-filled missing bm-prd-creator backlink), pattern-scale-adaptive-planning (+nano-spec — a fixed middle tier on the no-spec→nano→full-spec spectrum, the pattern applied at the methodology level; now 3-framework), pattern-session-handoff (+nano-spec — the always-current 4-file pack is the handoff; now 4-framework).
STAGE re-derivation: no new stage / split / merge / retire (small, single-stage ingest); no parked split candidate cleared. stage-specify (+nano-spec-create → 8-framework; aka +nano-spec; date 2026-07-13). nano-spec ships no stage-plan/stage-implement/stage-validate/stage-review/stage-release/stage-learn capability (its log.md is within-task journaling, not cross-iteration knowledge-compounding).
[2026-07-17] ingest | Superpowers (Jesse Vincent / Prime Radiant) — 14-skill methodology
Source: github.com/obra/superpowers @ v6.1.1 (Jesse Vincent, Prime Radiant; MIT; release announcement blog.fsck.com 2025-10-09). Raw: raw/superpowers/2026-07-17-superpowers.md (README + plugin.json + all 14 skills/*/SKILL.md verbatim; supporting files noted, not reproduced). A complete methodology from a small library — 14 skills, no personas, no commands, no deploy — made whole by a bootstrap (sp-using-superpowers) that forces skill invocation before any action; cross-harness (Claude Code/Codex/Cursor/Kimi/OpenCode/Pi/…).
Framework page framework/superpowers.md: the mandatory-skill bootstrap, the gated pipeline (brainstorm→worktree→plan→subagent-driven→TDD→review→finish), 4 philosophy pillars, capabilities by function, artifacts, patterns, See Also.
STAGE re-derivation: no new stage / split / merge / rename — Superpowers fits the existing 8 stages, touching 7 (no stage-specify: design folds into brainstorming→writing-plans, like GSD). Notable reinforcement: it is the 3rd framework (after Addy, gstack) with a clean functional-validate ∥ quality-review partition (verification-before-completion ∥ code-review), and the 4th framework in stage-learn (capability-compounding flavor). Split candidates unchanged: stage-govern (no constitution), stage-design (folds design in), stage-operate (no deploy). aka + dates → 2026-07-17 on stage-align/plan/implement/validate/review/release/learn.
[2026-07-19] docs | artifact index — visual map of the 34 artifacts
Not an ingest: no new source, no ontology/edge changes. Added a reader-facing index for the artifact/ namespace (the namespace had none; only sdlc-stage/ did).
NEW wiki/artifact/index.md: a whole-lifecycle flow overview Mermaid diagram of all 34 artifacts grouped by producing stage (solid leads-to/feeds/gates edges + dotted grounds-next-loop back-edges), then a stage-by-stage detail section — one Mermaid per SDLC stage, each in the layout that fits its artifacts (Align two-cluster · Specify hub-around-spec · Plan pipeline · Implement converge · Validate repair-loop · Review fan-in · Release converge/diverge · Learn hub + loop-back). Boundary artifacts from adjacent stages shown as dashed rounded nodes for context. Closes with a stage-ordered table of all 34 (Obsidian wikilinks) + See Also.
Each of the 8 stage-detail section headings links to its stage page (../sdlc-stage/stage-<x>.md); all 8 targets verified.
Not an ingest: no new source. Resolved a slug asymmetry around the cross-framework CONTEXT.md clash. GSD’s phase-context artifact was slugged by filename (artifact-context-md) while MP’s was slugged by meaning (artifact-domain-model), implying the GSD page “owned” the canonical name when neither does.
Renamed wiki/artifact/artifact-context-md.md → artifact-phase-context.md (git mv); H1 retitled CONTEXT.md (phase context) → Phase context (CONTEXT.md) to mirror Domain model (CONTEXT.md) (meaning-first). Both CONTEXT.md artifacts are now filed by what they are; the colliding filename belongs to neither slug.
Reciprocal naming-conflict callouts and the Align-stage same filename, different artifact dotted edge left intact. Historical log entries above retain the old slug as-written.
Not an ingest: no new source, no ontology/edge changes. Added a visual summary of the schema itself at the top of CONVENTIONS.md (before the Node types table), since the diagram depicts the meta-model the conventions define — not the concrete articles the index.md files list.
NEW ## The ontology at a glance section: a Mermaid flowchart showing the 5 node types (framework/capability/sdlc-stage/artifact/pattern) and 6 stored edges (belongs_to/implements/produces/applies/delegates_to/equivalent_to), all originating from capability as the hub; plus a dashed derived-projection edge (sdlc-stage synthesized from implements-backlinks). Distinct node shapes per type; solid = stored frontmatter edge, dashed = derived. Cross-links to the Node types + Relationship vocabulary tables.
Diagram validated via @mermaid-js/mermaid-cli (renders clean).
Not an ingest: no new source. Corrected one capability’s implements: edge. mp-wayfinder maps an oversized effort as a tracker of investigation tickets that resolve decisions (“Plan, don’t do — tickets resolve decisions, not deliverables”) and hands its output to mp-to-spec / mp-to-tickets. Since mp-to-spec IS stage-specify, wayfinder must sit upstream of the spec — i.e. it shapes what to build (stage-align), not decompose-the-how (stage-plan). Fits stage-align’s definition (align on what to build and why; capture/lock decisions) as a large-scale decision-mapping flavor.
capability/mp-wayfinder.md: implements stage-plan → stage-align; See Also stage link + rationale; updated date.
sdlc-stage/stage-plan.md: removed the mp-wayfinder backlink; dropped wayfinder from the matt-pocock-skills aka; updated date.
sdlc-stage/stage-align.md: added mp-wayfinder backlink (decision-mapping flavor) under Matt Pocock; added wayfinder to the matt-pocock-skills aka; updated date.
framework/matt-pocock-skills.md: moved mp-wayfinder from the “Skills — plan” group to “Skills — align / elicitation & intake”.
index.md: mp-wayfinder row now reads “(align)”; updated date. Framework-count on both stages unchanged (MP already counted on each). No stage added/removed/renamed. artifact-issue.md left as-is (stage-neutral; wayfinder still produces tracker issues).
[2026-07-20] docs | SDLC index — framework × stage support matrix
Not an ingest: no new source, no ontology/edge changes. Added a second table to sdlc-stage/index.md: 11 frameworks (rows) × 8 canonical stages (columns), each cell an emoji support level. Derived mechanically from the implements: edges of every capability (framework = belongs_to, stage = implements), then graded.
Legend: 🟢 native (dedicated step / several capabilities) · 🟡 partial (1–2 caps, not a distinct phase) · 🔗 folded into an adjacent stage · ➖ none. Rows ordered by lifecycle coverage (gstack/CE/Superpowers full-8 at top → nano-spec point-tool at bottom).
Footnote captures nuance the emoji can’t: OpenSpec Release = spec-merge not deploy (gstack the only real deploy); folded cases (GSD/Superpowers/CE fold specify into Align/Plan; OpenSpec folds plan into propose); BM Skills + nano-spec are deliberate point tools. Consistent with the existing Note that GSD/OpenSpec/Spec Kit ship no Review and Spec Kit no Release.
Extended the framework × stage support matrix with a 9th Off-stage column: a count (not a support level — kept visually distinct from the 🟢/🟡/🔗/➖ stage cells) of each framework’s capabilities that map to no lifecycle stage. Counts: gstack 5, Matt Pocock 2, nano-spec 2, Addy 1, Superpowers 1, BM Skills 1; GSD/OpenSpec/Spec Kit/BMAD/Compound Engineering 0.
NEW ### Off-stage capabilities subsection: the 12 no-stage capabilities grouped by kind — routing/dispatch & bootstrap (the near-universal cluster: addy-using-agent-skills ↔ mp-ask-matt ↔ gstack-router ↔ sp-using-superpowers), session/context continuity (mp-handoff), spec-pack state ops (nano-spec-status/update), publishing & diagrams (gstack-diagram/make-pdf), tooling & self-maintenance (gstack-benchmark-models/upgrade, bm-favicon-creator).
Insight recorded: process-owning frameworks (GSD/OpenSpec/Spec Kit/BMAD/CE) keep everything on-lifecycle (zero off-stage); toolkit/marketplace-style ones ship standalone utilities around the pipeline. All 15 wikilinks verified.
[2026-07-26] ingest | Sandcastle + Warren — NEW runtime node type (execution layer)
Ontology extension (6th node type). Added runtime — the agent execution/orchestration substrate (sandbox isolation, parallelism, AFK autonomy, steering, persistence): where and how an agent runs, vs the process layer’s what. Motivated by the observation (confirmed with the user) that Sandcastle and Warren are a genuinely different entity type from the process frameworks: they ship no SDLC capabilities and would contribute nothing to stage synthesis if force-fit as frameworks. Rather than dilute framework or pollute the framework×stage matrix, they get their own layer.
The seam is pattern, not sdlc-stage. A runtime carries no belongs_to/implements/equivalent_to; it stores exactly one new edge — enables: (runtime → pattern[]) — the infra-side realization of patterns that capabilities apply at the process level. pattern pages now collect two backlink rosters: Applied by (capabilities) + Enabled by (infrastructure) (runtimes).
CONVENTIONS.md: opening scope para (added the execution layer); “ontology at a glance” now “Six node types, seven relationship edges”; Mermaid diagram gains RT{{runtime}} + RT -->|enables| PAT; node-types table + runtime subtypes (library|platform) + runtime frontmatter example + enables row in the relationship vocabulary + derived-edges note + naming-convention row; NEW ## The execution layer (runtimes) section (orthogonal layer, synthesis-as-matrix-not-nodes with a parked graduation trigger, runtime ingest workflow).
NEW raw/runtime/ with verbatim README captures: 2026-07-26-sandcastle.md, 2026-07-26-warren.md.
NEW wiki/runtime/:
sandcastle.md (subtype library) — Matt Pocock’s TS SDK; enables: worktree-isolation + autonomous-loop + wave-parallelism + session-handoff. The library pole.
warren.md (subtype platform) — Jaymin West’s self-hosted control plane (os-eco, v0.9.10); enables: autonomous-loop + worktree-isolation + knowledge-compounding + session-handoff. The platform pole.
index.md — layer overview + orchestration-concern comparison matrix (the runtime analogue of the stage synthesis) + broader-category note (Conductor, Container-use, Sculptor, os-eco siblings).
Deliberately not linked: pattern-fresh-context-subagents (these runtimes isolate the filesystem/process, not the agent’s context window — that’s worktree-isolation’s territory; the harness owns context).
index.md: intro now names six namespaces; NEW ## runtime section (2 rows + matrix pointer); 5 pattern rows annotated with their infra-side + dates bumped to 2026-07-26.
No stage added/renamed/retired (runtimes implement no stage). Stage set unchanged at 8.
Verification: dangling-wikilink check across wiki/ — clean; every [[sandcastle]]/[[warren]] and enables: target resolves.
[2026-07-31] ingest | Claude Code — NEW harness node type (agent-program layer) — SCHEMA + PROOF PAGE
Ontology extension (7th node type). Added harness — the agent program itself (Claude Code, pi, OpenCode, …): the loop that loads a framework’s skills/commands and drives the model’s tool-call cycle. Motivated (confirmed with the user) by the observation that the two existing layers were already defined against it — frameworks were described as “cross-harness” and runtimes as “harness-agnostic” — yet it had no node. It is the middle/pivot layer: not a framework (ships execution primitives, not an SDLC methodology) and not a runtime (it is the thing runtimes spawn/wrap, one layer up).
Two new stored edges + a second enables domain.framework --runs_on--> harness[] (the first forward edge a framework page stores — turns “cross-harness” prose into structure) and runtime --runs--> harness[] (turns “harness-agnostic” prose into structure). harness --enables--> pattern[] reuses the enables edge (now domain = runtime or harness), so pattern pages gain a third backlink roster: Provided by (harness) alongside Applied by (capabilities) and Enabled by (infrastructure) (runtimes). “Ontology at a glance” now reads “Seven node types, nine relationship edges.”
CONVENTIONS.md: opening scope para (two substrate layers, harness as pivot); “ontology at a glance” para + Mermaid (HAR{{harness}} + FW -->|runs_on| HAR, RT -->|runs| HAR, HAR -->|enables| PAT); node-types table + harness subtypes (terminal|ide) + harness frontmatter example + framework-now-carries-runs_on note + runs_on/runs/broadened-enables rows in the relationship vocabulary + derived-edges note (harness is both target and source, like capability) + naming-convention row; NEW ## The harness layer section (framework/runtime boundary test, synthesis-as-matrix-not-nodes with parked graduation trigger, harness ingest workflow).
NEW raw/harness/2026-07-31-claude-code.md — source capture from Anthropic Claude Code docs + Agent SDK.
index.md: intro now names seven namespaces; NEW ## harness section (claude-code row + matrix pointer); ## runtime blurb now also points through the harnesses it runs:.
No stage added/renamed/retired (a harness implements no stage). Stage set unchanged at 8.
STAGED — remaining work (the “rest”, pending user review of the shape):
Ingest pi and OpenCode as full pages (turns the one-column matrix into a real cross-harness comparison).
Fleet-wide runs_on: wiring across the other 9 frameworks (GSD/CE/Addy/BMAD/SpecKit/OpenSpec/BM/nano-spec/matt-pocock) + bump their updated:/index rows.
Extend runs: on sandcastle/warren to the full provider lists (needs Codex/Cursor/OpenCode/Copilot/pi pages or stubs so nothing dangles — currently only [[claude-code]] wired to keep the dangling-link check clean).
Verification: dangling-wikilink check across wiki/ — clean; every [[claude-code]] reference resolves. Not-yet-paged harnesses (pi, opencode, codex, cursor, copilot) are named in bold plain text (runtime “broader category” precedent), never as wikilinks, so nothing dangles.
[2026-07-31] ingest | pi + OpenCode harnesses; fleet-wide runs_on:; “officially supported” rule — completes the harness layer
Completes the STAGED work from the proof slice above, after user review of the shape. User decision recorded: runs_on: / runs: link only to officially supported/documented harnesses, not any a framework could theoretically run on.
Convention (CONVENTIONS.md):runs_on/runs vocab rows now say “officially supports/documents”; NEW Support scope paragraph — an edge = documented support; a supported harness with no page yet is recorded in prose (not a dangling edge) and wired when ingested, so stored edges trail documented support until every referenced harness has a page.
Two new harness pages (both subtype: terminal, MIT, model-agnostic), from web-researched raw captures raw/harness/2026-07-31-{opencode,pi}.md:
opencode.md — Anomaly (ex-SST); batteries-included + model-agnostic; enables: all four patterns (fresh-context-subagents, edit-guardrails, session-handoff, context-engineering). The open/model-agnostic pole.
pi.md — Zechner/Earendil; minimal core (4 tools; sub-agents/MCP/permissions/plan-mode excluded → extensions); enables:only session-handoff + context-engineering. The minimalist pole and the harness-layer counterpart to nano-spec.
The layer’s sharpest finding, now encoded:pattern-fresh-context-subagents and pattern-edit-guardrails are harness primitives in claude-code + opencode but absent from pi’s core — a pattern that is a primitive in some harnesses and not others. Both pattern pages’ harness rosters now carry an explicit Not pi bullet.
Fleet-wide runs_on: wired on all 11 framework pages (paged subset only — claude-code/opencode/pi), from cited official-support evidence per framework: claude-code+opencode+pi → compound-engineering, superpowers; claude-code+opencode → gsd, addy-agent-skills, gstack, nano-spec; claude-code-only → matt-pocock-skills, openspec, speckit, bmad, bm-skills.
runs: extended:sandcastle → claude-code+opencode+pi; warren → claude-code+pi (paged subset of their documented provider lists).
Cascade: the 4 enabled patterns’ Provided by (harness) rosters + sources/updated refreshed (opencode on all 4; pi on session-handoff + context-engineering). harness/index.md — 3-member table, 3-column capability matrix, NEW Framework support (runs_on: inverse) matrix (the central home for full documented-support lists incl. unpaged harnesses in plain text), updated patterns-supplied + broader-category. wiki/index.md — 3 harness rows; claude-code.md backlinks now list all 11 frameworks.
Unpaged-but-officially-supported harnesses (Codex, Cursor, Copilot, Gemini CLI, Kimi, Windsurf, Qwen, Antigravity, Factory Droid, sapling, …) recorded as plain text in the framework-support matrix + harness/index.md ingest queue, per the Support-scope rule — candidates for future ingest.
No stage change (harnesses implement no stage). Stage set unchanged at 8. Harness layer now: 3 pages.
Verification: dangling-wikilink check across wiki/ — clean (see below); every runs_on:/runs:/enables: edge target resolves to a page.
[2026-08-02] ingest | Factory Droid harness — the fourth terminal harness, the model-routing pole
New harness pagewiki/harness/factory-droid.md (subtype: terminal, proprietary), enables: all four patterns — fresh-context-subagents (Custom Droids: fresh context + own session + per-droid model, Task tool + run_in_background), edit-guardrails (autonomy levels off/low/medium/high via --auto + read-only review + hooks + approval workflows), session-handoff (own-session subagents + Sessions API + headless droid exec), context-engineering (AGENTS.md standard + skills + 40+ MCP servers + plugins).
The distinctive axis: model routing. Where claude-code is Anthropic-only and opencode/pi are “model-agnostic,” Droid makes routing between models first-class — Anthropic/OpenAI/Google/open-weight, mid-session swap, complexity-tiered per-subagent, BYOK, plus a free open-weight Droid Core tier. Second signature: Missions (harness-native multi-agent orchestration; noted runtime-adjacent per the boundary test). Primitive set is otherwise Claude-Code-shaped (Custom Droids/Skills/Hooks/Plugins ≈ 1:1).
runs_on: wired on the three individual-author cross-harness frameworks that officially name Factory Droid — compound-engineering, gstack, superpowers (moved from prose-only to stored edges; updated: bumped on all three).
Cascade: the 4 enabled patterns’ Provided by (harness) rosters + See-Also harness lines now include factory-droid. harness/index.md — 4-member table, 4-column capability matrix, model-access spectrum prose rewritten, framework-support matrix bolds factory-droid for CE/gstack/superpowers, patterns-supplied bullets + broader-category + ingest-queue updated (Factory Droid removed from queue; count 3→4). wiki/index.md — new factory-droid harness row.
No stage added/renamed/retired (a harness implements no stage). Stage set unchanged at 8. Harness layer now: 4 pages.
Verification: dangling-wikilink check across wiki/ — clean; every [[factory-droid]] reference resolves to the new page. Remaining unpaged-but-supported harnesses (Codex, Cursor, Copilot, Gemini CLI, Kimi, Windsurf, Qwen, Antigravity, sapling) still recorded as bold plain text per the Support-scope rule.
[2026-08-05] schema | NEW topic overlay layer + first topic (Fowler’s Harness Engineering)
Motivation: a recurring user question — how to make agents follow project conventions and refine that over time (rules files, standards docs, ADRs, verifiers, solution corpora, CLAUDE.md). Concluded it is not a new ontology node but a cross-cutting family already decomposed across artifact + pattern + harness; what was missing was (a) connective tissue and (b) a page-type for authored, top-down reference hubs (a “pattern that links patterns” would be a category error, since patterns are minted bottom-up from capability backlinks).
CONVENTIONS.md: added the topic layer — an eighth namespacetopic/ that is explicitly not one of the seven ontology node types but a curated overlay (Map of Content) sitting above the graph. New section “The topic layer (curated overlays)”: the four-way distinction (index / sdlc-stage / pattern / topic), the overlay rule (topics store no edges, are never evidence, and must not add authored “referenced-by” rosters to targets — Obsidian’s auto-backlink panel is fine), lean frontmatter (type: topic), the discipline (≥3 namespaces, few, hand-maintained), and an authoring note (no stage re-derivation, no backlink cascade). Added a naming-table row (topic-<name>) and an overlay note under the node-types table.
New:raw/reference/2026-08-05-fowler-harness-engineering.md (immutable capture of martinfowler.com/articles/harness-engineering.html) + wiki/topic/topic-harness-engineering.md. The topic adopts Fowler’s vocabulary — guides (feedforward) / sensors (feedback) closed by a steering loop; computational vs inferential controls; keep quality left — and threads it through existing wiki pages, while explicitly reconciling Fowler’s broad “harness” ≠ this wiki’s harness node. Flags two concepts the wiki lacks (harnessability / ambient affordances) as a candidate future pattern, and folds in the “as models improve, the authored guide layer thins to the non-derivable kernel” analysis.
Light vocab edits (cross-links, not new rosters):pattern-shift-left (“keep quality left”), pattern-plan-verification-loop + pattern-adversarial-review + pattern-evidence-before-claims (framed as sensors; computational-vs-inferential), each with a See-Also to the topic. pattern-context-engineering + pattern-knowledge-compounding See-Also to the topic (guide-delivery / steering-loop).
index.md: new ## topic section + intro note. No stage change (a topic implements none).
[2026-08-05] ingest | Agent OS (Builder Methods) — v3 standards/guide-layer framework; 9th specify-cluster member
Source → raw/agent-os/2026-08-05-agent-os.md (web-researched capture: buildermethods.com/agent-os sub-pages + github.com/buildermethods/agent-os README/CHANGELOG/git-tree/raw command files). Captured v3.0.0 (released 2026-01-20) — a major refocus: v3 retired v2’s implementation/orchestration commands (create-spec/create-tasks/execute-tasks) and all sub-agents, keeping only the standards + spec-shaping layer. A live example of the “delete the derivable, keep the non-derivable” thesis on topic-harness-engineering.
New frameworkwiki/framework/agent-os.md (runs_on: [[claude-code]]; Cursor/Windsurf/Codex/Antigravity in prose per support-scope). Brian Casel / Builder Methods (also ships bm-skills), MIT, ~5.2K★. Identity: a deliberately non-full-SDLC framework (with bm-skills + nano-spec) whose primary value is the persistent guide layer.
5 capability pages (all subtype: command, no sub-agents in v3): agent-os-discover-standards, agent-os-index-standards, agent-os-inject-standards (the three cross-cutting guide-layer commands — no canonical stage, implements: []); agent-os-plan-product (→ stage-align, product-direction flavor; equivalent_toce-strategy); agent-os-shape-spec (→ stage-specify, 9th specify-cluster member).
2 new artifacts:artifact-standards (the signature — declarative conventions + index.yml matcher; the advisory/mined counterpart to SpecKit’s gatedartifact-constitution) and artifact-product-docs (mission/roadmap/tech-stack; counterpart to CE’s STRATEGY.md).
equivalent_to cascade: added [[agent-os-shape-spec]] to all 8 existing specify-cluster members (addy-spec-driven-development, bm-prd-creator, bmad-prd, gstack-spec, mp-to-spec, openspec-propose, speckit-specify, nano-spec-create) + [[agent-os-plan-product]] to ce-strategy (reciprocal).
Pattern rosters: Agent OS added to pattern-context-engineering (flagship — inject/index/discover-standards), pattern-knowledge-compounding (standards-compounding via sync-to-profile), pattern-grilling (AskUserQuestion-only interaction), pattern-scale-adaptive-planning, pattern-spec-driven-development. artifact-spec-md gains shape-spec.
Stage re-derivation: no add/rename/split/merge/retire — stage set unchanged at 8. stage-align now 10 frameworks (plan-product, product-direction flavor); stage-specify now 9 (shape-spec, uniquely standards-binding). The stage-govern split candidate updated: Agent OS sharpens but does not advance it — its standards are externalized-but-advisory (injected, not gated), landing with CE on the “read as context” side; the gated bar stays at one framework (Spec Kit). Noted the real second cluster is likely “advisory externalized standards” (→ the guide layer).