project-spec-workflow
spec-design
Shorthand: spec-design. Draft a project-level specification as the planner Technician, for a greenfield project or for an existing project that adopts Builder Garage. Ask about intent rather than invent it, keep observed behavior apart from intended behavior, and list every unmade product decision as pending for the product-intent acceptor. Produce spec content only: the spec reaches docs/specs/ through a reviewed change whose governing issue names it, and its acceptance includes product-intent acceptance. A drafted spec never authorizes implementing it.
- Technician role
- planner
Technical details
- Source revision
- v0.4.0 · f078359
- Files
- SKILL.md, templates, templates/project-spec.md
Download the ZIP below, preserve the project-spec-workflow/ directory, and place it in a skill directory supported by your harness.
Hand-placed skills are unmanaged. Canonical skills resolve project choices through garage config validate, so configuration-dependent steps still need a valid project configuration and garage on PATH. Directly requested discovery does not require configuration for its discovery-applicability decision.
From a project with valid configuration and declared skill targets, install and verify the complete embedded canonical skill set, together with the manuals the project adopts:
garage config validate garage skills install garage skills verify
The CLI supports user-scope targets for Claude Code, Codex, and Copilot CLI, not individual-skill or project-scope installs. Harness path behavior was confirmed on macOS; Linux and Windows harness behavior remains unconfirmed. Existing unmanaged or modified copies require explicit replacement consent and a backup. See skill installation.
