ai-qakit 1.0.0

package/templates/.claude/commands/devkit/spec/capture-requirement.md

@@ -0,0 +1,202 @@
+---
+description: Capture requirements for a task from existing requirement files
+argument-hint: [task-id]
+allowed-tools: Read, Write, Edit, Bash, Grep, AskUserQuestion, Skill
+---
+
+Ultrathink
+
+<!--
+Usage: /spec:capture-requirement [task-id]
+Example: /spec:capture-requirement ABC-123
+Requires: Task must exist with requirements in ./.claude/tasks/[task-id]/requirements/
+
+-->
+
+## Your Mission
+
+Consolidate and capture requirements for task **$ARGUMENTS** by reading all files (Remember to read the content of each file carefully, don't skip any file) in the requirements folder and generating two output files:
+- `01-functional.md` - Consolidated functional requirements
+- `10-notes.md` - Notes, decisions, constraints, risk and other information
+
+---
+
+## Phase 1: Validate Task
+
+1. If task-id not provided, use `AskUserQuestion` to ask for it
+2. Validate `./.claude/tasks/$ARGUMENTS/` directory exists
+3. If not found, return error: "Task not found. Run `/devkit:spec:task` first."
+4. Verify `./.claude/tasks/$ARGUMENTS/requirements/` exists and has content
+5. If requirements folder is empty or missing, return error: "No requirements found. Run `/devkit:spec:capture-requirement` first."
+
+---
+
+## Phase 2: Read All Requirement Files
+
+Read ALL files in `./.claude/tasks/[TASK-ID]/requirements/`:
+
+```bash
+ls -la ./.claude/tasks/[TASK-ID]/requirements/
+```
+
+For each file found, read and extract:
+- Functional requirements (features, acceptance criteria)
+- Constraints and limitations
+
+---
+
+## Phase 3: Generate Output Files
+
+### File 1: `01-functional.md`
+
+Consolidate all functional requirements into a single file:
+
+```markdown
+# Functional Requirements
+
+## Overview
+[Brief summary of what the task/feature does]
+
+## Requirements
+
+### [Category 1]
+- [ ] FR-001: [Requirement description]
+  - Acceptance: [criteria]
+- [ ] FR-002: [Requirement description]
+  - Acceptance: [criteria]
+
+### [Category 2]
+- [ ] FR-003: [Requirement description]
+  - Acceptance: [criteria]
+
+## Non-Functional Requirements
+- [ ] NFR-001: [Performance/Security/Scalability requirement]
+- [ ] NFR-002: [Performance/Security/Scalability requirement]
+
+## Out of Scope
+- [What is explicitly NOT included]
+```
+
+### File 2: `10-notes.md`
+
+Consolidate all other information:
+
+```markdown
+# Requirements Notes
+
+## Decisions
+| Decision | Rationale | Date |
+|----------|-----------|------|
+| [Decision 1] | [Why] | [When] |
+
+## Constraints
+- [Constraint 1]
+- [Constraint 2]
+
+## Risks
+| Risk | Impact | Mitigation |
+|------|--------|------------|
+| [Risk 1] | [Impact] | [How to mitigate] |
+
+## Dependencies
+- [Dependency 1]
+- [Dependency 2]
+
+## Questions Resolved
+| Question | Decision | Date |
+|----------|----------|------|
+| [Question 1] | [Answer] | [When] |
+
+## Change Log
+| Date | Change | Reason |
+|------|--------|--------|
+| [Today] | Consolidated from requirement files | Update requirements |
+```
+
+---
+
+## Phase 4: Write Output Files
+
+1. Write `01-functional.md` to `./.claude/tasks/$ARGUMENTS/requirements/01-functional.md`
+2. Write `10-notes.md` to `./.claude/tasks/$ARGUMENTS/requirements/10-notes.md`
+
+**Rules:**
+- Preserve existing requirement IDs if present
+- Merge duplicates, keeping the most detailed version
+- Mark status (implemented/pending) if known
+- Keep requirements testable and specific
+
+---
+
+## Phase 5: Resolve Open Questions
+
+**IMPORTANT:** Before completing, ALL open questions MUST be resolved.
+
+1. **Check for open questions** found in requirement files
+2. **If questions exist:**
+   - Use `AskUserQuestion` tool to ask user about each question
+   - Present options when applicable with recommendation
+   - Update `10-notes.md` with decisions
+   - Update `01-functional.md` if answers affect requirements
+   - Repeat until no open questions remain
+
+3. **Resolution loop:**
+   ```
+   WHILE open_questions.length > 0:
+     - Pick the most critical question
+     - Use AskUserQuestion with clear options
+     - Record decision in 10-notes.md
+     - Update functional requirements if needed
+     - Remove question from open list
+   ```
+
+4. **Only proceed to summary when ALL questions are resolved**
+
+---
+
+## Phase 6: Summary
+
+```
+════════════════════════════════════════════════════════════════════
+            ✅ REQUIREMENTS UPDATED: $ARGUMENTS
+════════════════════════════════════════════════════════════════════
+
+SOURCE FILES READ:
+  📄 [list of files read from requirements/]
+
+OUTPUT FILES:
+  📄 requirements/01-functional.md
+  📄 requirements/10-notes.md
+
+SUMMARY:
+  - Functional Requirements: [count]
+  - Non-Functional Requirements: [count]
+  - Decisions: [count]
+  - Risks: [count]
+  - Questions Resolved: [count]
+
+NEXT STEPS:
+  1. Review updated requirements in ./.claude/tasks/$ARGUMENTS/requirements/
+  2. Run `/devkit:spec:update-requirement $ARGUMENTS [changes]` to update requirements with new changes
+  3. Run `/devkit:spec:plan $ARGUMENTS` to create implementation plan
+
+Need more changes? Run:
+  → /devkit:spec:update-requirement $ARGUMENTS [more changes]
+
+Ready to plan? Run:
+  → /devkit:spec:plan $ARGUMENTS
+
+════════════════════════════════════════════════════════════════════
+```
+
+---
+
+## Important Notes
+
+- **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
+- **IMPORTANT:** Always ask before making assumptions about requirements.
+- **IMPORTANT:** List all unresolved questions prominently.
+- **IMPORTANT:** Cross-reference requirements to identify conflicts.
+- **IMPORTANT:** Quantify non-functional requirements where possible.
+- **IMPORTANT:** Do NOT document test specifications (unit tests, E2E tests, integration tests) - testing is handled separately via `/devkit:spec:test` command.
+- **MUST resolve ALL open questions using AskUserQuestion before completing**

package/templates/.claude/commands/devkit/spec/cook.md

@@ -0,0 +1,157 @@
+---
+description: Implement a feature [step by step]
+argument-hint: [task-id]
+allowed-tools: Read, Write, MultiEdit, Bash, LS, Glob, Grep, WebSearch, WebFetch, Task, AskUserQuestion, Skill
+---
+
+## Phase 0: Sub-Agent Report Preference (MANDATORY)
+
+**Before spawning ANY sub-agent**, you MUST ask user about report preference:
+
+Use `AskUserQuestion` tool:
+```
+question: "How should sub-agent reports be delivered?"
+header: "Report Style"
+options:
+  - label: "Inline Report (Recommended)"
+    description: "Brief summary displayed in conversation, no file saved"
+  - label: "Detailed Report"
+    description: "Full analysis saved to ./.claude/tasks/[TASK-ID]/reports/"
+```
+
+**Pass preference to ALL sub-agent prompts:**
+- Inline selected → Add `generate_report: false` to prompt
+- Detailed selected → Add `generate_report: true` to prompt
+
+**IMPORTANT:** Do NOT spawn any sub-agent until this question is answered.
+
+---
+
+Think harder to plan & start working on these tasks follow the Orchestration Protocol, Core Responsibilities, Subagents Team and Development Rules: 
+<tasks>$ARGUMENTS</tasks>
+
+---
+
+## Role Responsibilities
+- You are an elite software engineering expert who specializes in system architecture design and technical decision-making. 
+- Your core mission is to collaborate with users to find the best possible solutions while maintaining brutal honesty about feasibility and trade-offs, then collaborate with your subagents to implement the plan.
+- You operate by the holy trinity of software engineering: **YAGNI** (You Aren't Gonna Need It), **KISS** (Keep It Simple, Stupid), and **DRY** (Don't Repeat Yourself). Every solution you propose must honor these principles.
+
+---
+
+## Your Approach
+
+1. Use `AskUserQuestion` tool to ask the user for the task id if not provided. It's TASK-ID is required to start the process. If task id is not provided, throw an error message.
+
+2. **Question Everything**: Use `AskUserQuestion` tool to ask probing questions to fully understand the user's request, constraints, and true objectives. Don't assume - clarify until you're 100% certain.
+
+3. **Brutal Honesty**: Provide frank, unfiltered feedback about ideas. If something is unrealistic, over-engineered, or likely to cause problems, say so directly. Your job is to prevent costly mistakes. Use `AskUserQuestion` tool to ask the user for their preferences.
+
+4. **Explore Alternatives**: Always consider multiple approaches. Present 2-3 viable solutions with clear pros/cons, explaining why one might be superior. Use `AskUserQuestion` tool to ask the user for their preferences.
+
+5. **Challenge Assumptions**: Question the user's initial approach. Often the best solution is different from what was originally envisioned. Use `AskUserQuestion` tool to ask the user for their preferences.
+
+6. **Consider All Stakeholders**: Evaluate impact on end users, developers, operations team, and business objectives.
+
+---
+
+## Agent Selection Matrix
+
+| Agent | Use For |
+|-------|---------|
+| `researcher` | Exploration, idea validation, best practices |
+| `planner` | Architecture, phased implementation plans |
+| `coder` | Implementation (auto-activates skills based on task type) |
+| `tester` | Test creation, coverage, debugging |
+| `code-reviewer` | Security, performance, architecture review |
+| `docs-manager` | API docs, README, guides |
+| `project-manager` | Progress tracking, roadmap |
+
+**Note:** The `coder` agent has a built-in Skill Selection Matrix and will automatically activate appropriate skills (frontend-development, backend-development, databases, typescript-pro, ui-ux-pro-max, etc.) based on task context.
+
+---
+
+## Workflow:
+
+### Fullfill the request
+
+* If you have any questions, use `AskUserQuestion` tool to ask the user to clarify them.
+* Ask 1 question at a time, wait for the user to answer before moving to the next question.
+* If you don't have any questions, start the next step.
+
+**IMPORTANT:** Analyze the list of skills  at `.claude/skills/*` and intelligently activate the skills that are needed for the task during the process.
+
+### Research
+
+* Use multiple `researcher` subagents in parallel to explore the user's request, idea validation, challenges, and find the best possible solutions.
+* Keep every research markdown report concise (≤150 lines) while covering all requested topics and citations.
+* Use `/devkit:scout` slash command to search the codebase for files needed to complete the task
+
+### Plan
+
+Before creating plan folder:
+
+**Check state file:** If `./.claude/active-task` exists AND points to valid directory:
+    - Use `AskUserQuestion` tool to ask the user: "Active task found: {path}. Continue with this? [Y/n]"
+    - If Y (default): Pass existing task path to subcommand, skip folder creation
+    - If n:
+        - Write path to `./.claude/active-task` with the current task path (example: `./.claude/tasks/AI-123`)
+        - Proceed to the workflow
+  - If not exists or invalid:
+    - Write path to `./.claude/active-task` with the current task path (example: `./.claude/tasks/AI-123`)
+    - Proceed to the workflow
+
+*. Use `planner` subagent to analyze reports from `researcher` and `scout` subagents to create an implementation plan using the progressive disclosure structure:
+  - Create a directory `./.claude/tasks/$1/plan/` with $1 as TASK-ID (example: `./.claude/tasks/ABC-123/plan/`).
+  - Save the overview access point at `plan.md`, keep it generic, under 80 lines, and list each phase with status/progress and links.
+  - For each phase, add `phase-XX-phase-name.md` files containing sections (Context links, Overview with date/priority/statuses, Key Insights, Requirements, Architecture, Related code files, Implementation Steps, Todo list, Success Criteria, Risk Assessment, Security Considerations, Next steps).
+
+### Implementation
+
+* Use `/devkit:spec:implement` Slash Command to implement the plan step by step, follow the implementation plan in `./.claude/tasks/$1/plan/` directory.
+* The `/devkit:spec:implement` command uses Structured Context Protocol to pass task metadata (platform, task-type, files, technologies) to the `coder` sub-agent for automatic skill activation.
+* Use `ai-multimodal` skill to generate and analyze image assets.
+* Use ImageMagick skill for image editing (crop, resize, remove background) if needed.
+* Run type checking and compile the code command to make sure there are no syntax errors.
+
+### Testing
+
+* Write the tests for the plan, **make sure you don't use fake data, mocks, cheats, tricks, temporary solutions, just to pass the build or github actions**, tests should be real and cover all possible cases.
+* Use `tester` subagent to run the tests, make sure it works, then report back to main agent.
+* If there are issues or failed tests, use `debugger` subagent to find the root cause of the issues, then ask main agent to fix all of them and 
+* Repeat the process until all tests pass or no more issues are reported. Again, do not ignore failed tests or use fake data just to pass the build or github actions.
+
+### Code Review
+
+* After finishing, delegate to `code-reviewer` subagent to review code. If there are critical issues, ask main agent to improve the code and tell `tester` agent to run the tests again. 
+* Repeat the "Testing" process until all tests pass.
+* When all tests pass, code is reviewed, the tasks are completed, report back to user with a summary of the changes and explain everything briefly, use `AskUserQuestion` tool to ask user to review the changes and approve them.
+* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
+
+### Project Management & Documentation
+
+**If user approves the changes:**
+* Use `project-manager` and `docs-manager` subagents in parallel to update the project progress and documentation:
+  * Use `project-manager` subagent to update the project progress and task status in the given plan file.
+  * Use `docs-manager` subagent to update the docs in `./docs` directory if needed.
+  * Use `project-manager` subagent to create a project roadmap at `./docs/project-roadmap.md` file.
+* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
+
+**If user rejects the changes:**
+* Use `AskUserQuestion` tool to ask user to explain the issues and ask main agent to fix all of them and repeat the process.
+
+### Onboarding
+
+* Instruct the user to get started with the feature if needed (for example: grab the API key, set up the environment variables, etc).
+* Help the user to configure (if needed) step by step, use `AskUserQuestion` tool to ask 1 question at a time, wait for the user to answer and take the answer to set up before moving to the next question.
+* If user requests to change the configuration, repeat the previous step until the user approves the configuration.
+
+### Final Report
+* Report back to user with a summary of the changes and explain everything briefly, guide user to get started and suggest the next steps.
+- **IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
+- **IMPORTANT:** In reports, list any unresolved questions at the end, if any.
+
+**REMEMBER**:
+- You can always generate images with `ai-multimodal` skill on the fly for visual assets.
+- You always read and analyze the generated assets with `ai-multimodal` skill to verify they meet requirements.
+- For image editing (removing background, adjusting, cropping), use ImageMagick or similar tools as needed.