project-specification

## Delegation For detailed specification writing workflows, this skill delegates to `spec-kit:spec-writing` as the canonical implementation. Use this skill for quick specification needs; use spec-kit for comprehensive specification documents. ## When To Use - After brainstorming phase completes - Have project brief but need detailed requirements - Need testable acceptance criteria for implementation - Planning validation and testing strategy - Translating business requirements into technical specs - Defining scope boundaries and out-of-scope items ## When NOT To Use - Still exploring problem space (use `Skill(attune:project-brainstorming)` instead) - Already have detailed specification (use `Skill(attune:project-planning)` instead) - Refining existing implementation (use code review skills) - Making strategic decisions (use `Skill(attune:war-room)` for complex choices) ## Integration **With spec-kit**: - Delegates to `Skill(spec-kit:spec-writing)` for methodology - Uses spec-kit templates and validation - Enables clarification workflow **Without spec-kit**: - Standalone specification framework - Requirement templates - Acceptance criteria patterns ## Post-Completion: Workflow Continuation (REQUIRED) **Automatic Trigger**: After Quality Checks pass and `docs/specification.md` is saved, MUST auto-invoke the next phase. **When continuation is invoked**: 1. Verify `docs/specification.md` exists and is non-empty 2. Display checkpoint message to user: ``` Specifica...