new-requirement
The `new-requirement` slash command scaffolds a structured feature development workflow by guiding users through requirements capture, documentation initialization, and design planning. Use it when starting a new feature to systematically define the problem, explore implementation approaches, document architecture decisions, and break work into estimated tasks while leveraging project-specific conventions stored in AI DevKit memory.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/codeaholicguy/ai-devkit/HEAD/commands/new-requirement.md -o ~/.claude/commands/new-requirement.mdnew-requirement.md
Guide me through adding a new feature, from requirements documentation to implementation readiness.
1. **Use AI DevKit Memory for Context** — Search AI DevKit memory (not built-in memory) for related decisions or conventions via `npx ai-devkit@latest memory search --query "<feature/topic>"` and reuse relevant context. If unfamiliar, check the AI DevKit memory skill first.
2. **Capture Requirement** — Ask for: feature name (kebab-case, e.g., `user-authentication`), problem it solves, who uses it, key user stories. **Brainstorm**: ask clarifying questions as needed, explore alternatives to confirm this is the right thing to build, then present 2–3 approaches with one-line trade-offs and a recommendation.
3. **Initialize Feature Documentation Structure** — Run `npx ai-devkit@latest docs init-feature {name}` and fill the returned paths. It uses configured phases. If unavailable, copy each configured phase `README.md` to `docs/ai/{phase}/feature-{name}.md`, preserving frontmatter and headings.
4. **Requirements Phase** — Fill out the generated or selected requirements doc: problem statement, goals/non-goals, user stories, success criteria, constraints, open questions.
5. **Design Phase** — Fill out the generated or selected design doc: architecture changes, data models, API/interfaces, components, design decisions, security and performance considerations.
6. **Planning Phase** — Fill out the generated or selected planning doc: task breakdown with subtasks, dependencies, effort estimates, implementation order, risks.
7. **Store Reusable Knowledge** — When important conventions or decisions are finalized, store them via `npx ai-devkit@latest memory store --title "<title>" --content "<knowledge>" --tags "<tags>"`.
8. **Next Command Guidance** — Run `/review-requirements` first, then `/review-design`. If both pass, continue with `/execute-plan`.AI DevKit · Compare implementation with design and requirements docs to ensure alignment.
AI DevKit · Pre-push code review against design docs.
AI DevKit · Execute a feature plan task by task.
AI DevKit · Store reusable guidance in the knowledge memory service.
AI DevKit · Review feature design for completeness.
AI DevKit · Review feature requirements for completeness.
AI DevKit · Update planning docs to reflect implementation progress.
AI DevKit · Add tests for a new feature.