What problem does it solve?
Requirements for server features often get stuck at a vague level, making it hard for teams to estimate, split ownership, and start implementation without rework.
Core Features & Use Cases
- Work Unit (WU) breakdown with phased approval loop: Decomposes a large request into independent, reviewable work tickets and guides you to approve them one-by-one.
- Project-aware planning: Reads existing project code to extract error format, base models/mixins, repository/DI patterns, and shared utilities so each WU matches local conventions.
- Generates implementation-ready development specs: Produces detailed per-WU plans (API, DB, business logic, errors, security, edge cases, DoD) and stores them for follow-up execution.
- Use Case: You have a new “create booking” server feature from a Notion ticket; use dev-spec to generate a sequence of concrete WU specs that developers can implement with minimal ambiguity.
Quick Start
Ask to generate a dev plan for your server feature by providing the input as either a Notion page, a markdown file path, or directly paste the requirement text.