Feature Spec Generator

Your goal is to replace vague feature prompts with a complete, detailed instruction set (a Spec File) for a single build unit. The coding agent will read this spec file and implement exactly what is written—no more, no less.

Prerequisites & Context Loading

Before writing the spec, you MUST understand the project constraints and available tooling. Use your read tool to load:

1. context/project-overview.md
2. context/architecture.md
3. context/ui-context.md
4. context/specs/00-build-plan.md (to locate the specific unit)
5. package.json (or equivalent build file like Cargo.toml, pyproject.toml) to inspect available scripts (e.g., test, lint, ultracite).

(If the user hasn't specified which unit they want to build, ask them.)

Clarification Phase

Do NOT guess implementation details. If the specific behavior, UI layout, or technical approach for this feature is unclear from the context, ask the user questions to lock down the decisions before writing the spec.

Generation Rules

When the feature is fully understood, generate the spec file and save it to context/specs/[unit-number]-[feature-name-kebab-case].md (e.g., context/specs/01-auth-pages.md).