spec-writing
Spec Writing
Overview
Create clear, complete, and testable specifications from natural language feature descriptions. Specifications focus on user value and business needs, avoiding implementation details.
When To Use
- Creating new feature specifications
- Refining existing specifications
- Writing user stories and acceptance criteria
- Defining success criteria
When NOT To Use
- Generating implementation tasks - use task-planning
Core Principles
Focus on user value and business needs rather than implementation details. Avoid specifying technology choices in requirement definitions unless strictly necessary. Ensure every requirement is testable and verifiable with measurable criteria. Limit clarification markers; make informed assumptions based on industry standards and document them explicitly.
More from athola/claude-night-market
project-planning
Turn a specification into a phased implementation plan with dependency ordering.
126code-quality-principles
KISS, YAGNI, and SOLID code quality principles for clean code, reducing complexity and preventing over-engineering.
94project-brainstorming
Guide project ideation via Socratic questioning to generate project briefs.
92doc-generator
Generate or remediate documentation with human-quality writing and style.
81rigorous-reasoning
Anti-sycophancy reasoning checklist.
79project-specification
Transform project briefs into testable specifications with user stories, acceptance criteria, and measurable outcomes.
78