spec-template
Product Spec Template
A structured 9-section template for defining software product specifications.
When to Use
- Starting a new project from a one-liner idea
- Converting rough notes into a formal specification
- Reviewing spec completeness before implementation
- Ensuring consistent spec format across projects
The 9 Sections
Section Structure
Every spec.md should include these sections:
## 🎯 [Product Name]
More from b1tank/skills
market-research
Research existing products and competitors for a given product idea. Use when starting a new project, cloning an existing product, or analyzing competitive landscape. Returns feature analysis, gaps, and differentiation opportunities.
15diff-check
Author's cleanup checklist before committing or submitting a PR. Use before any commit or PR to ensure code is clean, focused, and ready for review. Checks for debug code, secrets, redundant changes, and scope creep.
13decompose-task
Break large tasks (>100 lines) into atomic, verifiable sub-tasks. Use when a task scope is unclear, touches multiple files/modules, or exceeds comfortable single-commit size. Returns structured breakdown without implementing code.
8skill-name
Clear description of what this skill does and when to use it. Include specific triggers and contexts for when Claude should invoke this skill.
5clone-with-hash
Clone a local or remote git repo into a new folder with a short random hash suffix (e.g., -a1b2c3) and immediately create a new branch from a base branch. Use when a user wants a separate workspace to avoid conflicts, especially for parallel feature work or multiple local clones.
2