Requirements

Pre-implementation thinking tool for complex features. Produces disposable requirements artifacts — specs are thinking tools, not sources of truth. Once implemented, the code absorbs and replaces them.

Scope boundary: This skill defines what to build. For how to plan the implementation, see /code-planning. For domain modeling decisions, see /domain-design (section 10 pre-design checklist). For the end-to-end build pipeline, check the project's CLAUDE.md for a feature pipeline skill.

When to use

Use this skill before implementation when a feature involves:

• A new domain entity or aggregate
• Multiple new endpoints working together
• A new domain concept that needs naming and boundary definition
• Cross-cutting behavior changes (e.g., new permission model, new currency support)
• Features where edge cases are non-obvious

Skip this skill for: