Skip to content

Commit 4a26455

Browse files
committed
feat(skills): update dev-lifecycle new requirement brainstorming
1 parent bc649d9 commit 4a26455

4 files changed

Lines changed: 103 additions & 148 deletions

File tree

commands/new-requirement.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,8 @@ description: Scaffold feature documentation from requirements through planning.
44

55
Guide me through adding a new feature, from requirements documentation to implementation readiness.
66

7-
1. **Capture Requirement**If not already provided, ask for: feature name (kebab-case, e.g., `user-authentication`), what problem it solves and who will use it, and key user stories.
8-
2. **Use Memory for Context**Before asking repetitive clarification questions, search memory for related decisions or conventions via `npx ai-devkit@latest memory search --query "<feature/topic>"` and reuse relevant context.
7+
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.
8+
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.
99
3. **Create Feature Documentation Structure** — Copy each template's content (preserving YAML frontmatter and section headings) into feature-specific files:
1010
- `docs/ai/requirements/README.md``docs/ai/requirements/feature-{name}.md`
1111
- `docs/ai/design/README.md``docs/ai/design/feature-{name}.md`

0 commit comments

Comments
 (0)