Specs CLI IP-100-harness-methodology-domain Implementation Notes
Expanded the Harness domain from one concept page into a sectioned methodology domain.
Added source concept pages for foundations, prompt surfaces, skill packs, execution modes, validation/tools, and phase/goal workflow.
Added source lifecycle flow pages covering adoption, requirements, planning, delivery, validation, review, debugging, docs maintenance, issue reporting, baseline publishing, and update.
Projected the domain into Fumadocs with readable section navigation under /docs/harness.
Preserved CLI mechanics as a linked separate domain.
Parallel discovery and plan-shaped parallel content ownership. Navigation was locked first, then concept and flow source pages were treated as disjoint write scopes before shared routed projection and validation.
Compact concept pages intentionally cover multiple related concepts to avoid a v1 page for every individual skill.
Flow coverage is organized into three lifecycle pages rather than one page per workflow, because IP-121 asks for readable human-facing flows rather than worker-task decomposition.
Check Result Notes jq empty on changed meta.json filesPassed Harness section navigation is valid JSON. bun run checkPassed Repo lint/format check. bun run check-typesPassed Includes wiki typecheck. bun run build --filter=@punks/wikiPassed Harness routes included in static build. Local browser smoke Passed /docs/harness and section pages render.
Criterion Status Evidence Sectioned harness navigation Done apps/wiki/content/docs/harness/meta.json and section index pages.Concept inventory represented Done Source/routed concept pages cover IP-120 required concepts. Skill packs modeled before individual skills Done skill-packs page covers pack model and avoids per-skill inventory.Lifecycle flows represented Done Three lifecycle source/routed flow pages cover IP-121 checklist. CLI mechanics separated Done Harness pages link to CLI domain for mechanics instead of duplicating implementation details. Future docs-ingest compatible Done Domain source index lives under apps/wiki/content/docs/project/domains/harness; routed pages summarize/link.
Area Check How to perform Expected result Navigation Confirm harness is not a flat wall Open /docs/harness Six readable sections are visible. Concepts Confirm concept coverage Open one page in each concept section Required IP-120 concepts are explained and internally scoped. Flows Confirm lifecycle coverage Open /docs/harness/lifecycle-flows pages Adoption, requirements, delivery, review/debug, docs, report, baseline, and update flows are covered. Separation Confirm CLI mechanics stay separate Follow links to /docs/cli CLI mechanics remain in CLI domain.
Future implemented specs may split compact concept/flow pages when they produce deeper source truth.