Project Specification
Productivityproject-specificationProject Specification is an Agent Skill for productivity published in the athola/claude-night-market repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Transforms project briefs into testable specifications with user stories and acceptance criteria. Use after brainstorming, before planning.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/athola/claude-night-market/blob/HEAD/plugins/attune/skills/project-specification/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/project-specification, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
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 thorough 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
Record the Tradeoff (decision journal)
If the specification settled a design decision with real alternatives (a chosen
data model, an interface boundary, a constraint accepted), record it to
docs/tradeoffs.md before continuing (draft and confirm):
- If leyline is installed, invoke
Skill(leyline:decision-journal)and append a tradeoff entry (the decision, the options weighed, and what was sacrificed; setphasetospecify). Show the draft; append on confirmation. - Fallback (leyline absent): append to
docs/tradeoffs.mdusing the in-file ENTRY TEMPLATE; assign the nextTR-NNNid.
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:
- Verify
docs/specification.mdexists and is non-empty - Display checkpoint message to user:
Specification complete. Saved to docs/specification.md. Proceeding to planning phase... - Invoke next phase:
Skill(attune:project-planning)
Bypass Conditions (ONLY skip continuation if ANY true):
--standaloneflag was provided by the userdocs/specification.mddoes not exist or is empty (phase failed)- User explicitly requests to stop after specification
Do NOT prompt the user for confirmation: this is a lightweight checkpoint, not an interactive gate. The user can always interrupt if needed.
Exit Criteria
-
docs/specification.mdexists, is non-empty, and passes Quality Checks. - Every functional requirement has testable acceptance criteria.
- Any design decision with real alternatives is recorded to
docs/tradeoffs.md(or there was no meaningful design fork). - The next phase is auto-invoked unless a bypass condition holds.
Related Skills
Skill(spec-kit:spec-writing)- Spec-kit methodology (if available)Skill(attune:project-brainstorming)- Previous phaseSkill(attune:project-planning)- AUTO-INVOKED next phase after specificationSkill(attune:mission-orchestrator)- Full lifecycle orchestration
Related Commands
/attune:specify- Invoke this skill/attune:specify --clarify- Run clarification workflow/attune:blueprint- Next step in workflow
Examples
See /attune:specify command documentation for complete examples.