Agent skill
specify-meta
Scaffold, status-check, and manage specification directories. Handles auto-incrementing IDs, README tracking, phase transitions, and decision logging in .start/specs/. Falls back to docs/specs/ for legacy specs. Used by both specify and implement workflows.
Install this agent skill to your Project
npx add-skill https://github.com/rsmdt/the-startup/tree/main/plugins/start/skills/specify-meta
SKILL.md
Persona
Act as a specification workflow orchestrator that manages specification directories and tracks user decisions throughout the PRD → SDD → PLAN workflow.
Interface
SpecStatus { id: string // 3-digit zero-padded (001, 002, ...) name: string directory: string // .start/specs/[NNN]-[name]/ (legacy: docs/specs/) phase: Initialization | PRD | SDD | PLAN | Ready documents: { name: string status: pending | in_progress | completed | skipped notes?: string }[] }
State { specId = "" currentPhase: Initialization | PRD | SDD | PLAN | Ready documents: [] }
Constraints
Always:
- Use spec.py (co-located with this SKILL.md) for all directory operations.
- Create README.md from template.md when scaffolding new specs.
- Log all significant decisions with date, decision, and rationale.
- Confirm next steps with user before phase transitions.
Never:
- Create spec directories manually — always use spec.py.
- Transition phases without updating README.md.
- Skip decision logging when user makes workflow choices.
Reference Materials
- Spec Management — Spec ID format, directory structure, script commands, phase workflow, decision logging, legacy fallback
- README Template — Template for spec README.md files
Workflow
1. Scaffold
Create a new spec with an auto-incrementing ID.
- Run
Bash("spec.py \"$featureName\""). - Create README.md from template.md.
- Report the created spec status.
2. Read Status
Read existing spec metadata.
- Run
Bash("spec.py \"$specId\" --read"). - Parse TOML output into SpecStatus.
- Suggest the next continuation point:
match (documents) { plan exists => "PLAN found. Proceed to implementation?" sdd exists, no plan => "SDD found. Continue to PLAN?" prd exists, no sdd => "PRD found. Continue to SDD?" no documents => "Start from PRD?" }
3. Transition Phase
Update the spec directory to reflect the new phase.
- Update README.md document status and current phase.
- Log the phase transition in the decisions table.
- Hand off to the document-specific skill:
match (phase) { PRD => specify-requirements skill SDD => specify-solution skill PLAN => specify-plan skill }
- On completion, return here for the next phase transition.
4. Log Decision
Append a row to the README.md Decisions Log table. Update the Last Updated field.
Entry Point
match ($ARGUMENTS) { featureName (new) => execute step 1 (Scaffold) specId (existing) => execute steps 2, 3, and 4 in order }
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
specify
Create a comprehensive specification from a brief description. Manages specification workflow including directory creation, README tracking, and phase transitions.
debug
Systematically diagnose and resolve bugs through conversational investigation and root cause analysis
analyze
Discover and document business rules, technical patterns, and system interfaces through iterative analysis
specify-solution
Create and validate solution design documents (SDD). Use when designing architecture, defining interfaces, documenting technical decisions, analyzing system components, or working on solution.md files in .start/specs/. Includes validation checklist, consistency verification, and overlap detection.
implement
Executes the implementation plan from a specification. Loops through plan phases, delegates tasks to specialists, updates phase status on completion. Supports resuming from partially-completed plans.
review
Multi-agent code review with specialized perspectives (security, performance, patterns, simplification, tests)
Didn't find tool you were looking for?