@amrhas82/agentic-kit 2.0.0 → 2.3.0

package/CHANGELOG.md

@@ -17,6 +17,20 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ---
 
+## [2.3.0] - 2026-01-22
+
+### Removed
+- Removed `subagent-spawning` skill (functionality integrated into agents)
+
+### Changed
+- Updated command/skill count from 21 to 20 across all documentation
+- README.md: Updated command counts and removed subagent-spawning from skill list
+- installer/cli.js: Updated welcome banner to reflect 20 commands
+- package.json: Updated description to reflect 20 commands
+- packages/subagentic-manual.md: Updated command counts
+
+---
+
 ## [1.11.1] - 2026-01-20
 
 ### Fixed
@@ -404,6 +418,7 @@ npx @amrhas82/agentic-kit
 
 | Version | Date | Key Features |
 |---------|------|--------------|
+| **2.3.0** | 2026-01-22 | Removed subagent-spawning skill (20 commands) |
 | **1.11.1** | 2026-01-20 | Fixed missing commands in opencode.jsonc |
 | **1.11.0** | 2026-01-20 | Added /stash command (21 total commands) |
 | **1.2.1** | 2025-11-05 | Package optimization, repository cleanup |

package/README.md

@@ -9,7 +9,7 @@
          ╚═╝  ╚═╝ ╚═════╝ ╚══════╝╚═╝  ╚═══╝   ╚═╝   ╚═╝ ╚═════╝    ╚═╝  ╚═╝╚═╝   ╚═╝
 ```
 
-**AI development toolkit with 11 specialized agents and 21 commands per tool**
+**AI development toolkit with 11 specialized agents and 20 commands per tool**
 
 </div>
 
@@ -36,15 +36,15 @@ npm install -g @amrhas82/agentic-kit
 agentic-kit
 
 # Choose tool(s): claude, opencode, ampcode, or droid
-# Each tool gets 11 agents + 21 commands
+# Each tool gets 11 agents + 20 commands
 ```
 
 ### Supported Tools
 
-- **Claude Code** - 11 subagents + 11 skills + 10 commands
-- **Opencode** - 11 agent references + 21 commands
-- **Ampcode** - 11 subagents + 11 skills + 10 commands
-- **Droid** - 11 agent references + 21 commands
+- **Claude Code** - 11 subagents + 10 skills + 10 commands
+- **Opencode** - 11 agent references + 20 commands
+- **Ampcode** - 11 subagents + 10 skills + 10 commands
+- **Droid** - 11 agent references + 20 commands
 
 **Key Difference:**
 - **Claude Code / Ampcode**: Full subagent system with orchestrator + skills (auto-triggering)
@@ -86,13 +86,12 @@ agentic-kit
 - **system-architect** - System design, technology selection, API design, scalability planning
 - **ui-designer** - UI/UX design, wireframes, prototypes, accessibility, design systems
 
-### 21 Commands/Skills
+### 20 Commands/Skills
 
-**Auto-Triggering Skills (4)** - Claude Code only:
+**Auto-Triggering Skills (3)** - Claude Code only:
 - **test-driven-development** - Write test first, watch fail, minimal passing code
 - **testing-anti-patterns** - Prevent mocking anti-patterns
 - **verification-before-completion** - Verify before claiming done
-- **subagent-spawning** - TDD-aware templates for fresh subagents
 
 **Manual Skills/Commands (17):**
 - **brainstorming** - Structured brainstorming sessions
@@ -157,7 +156,7 @@ agentic-kit
 ## 📊 Stats
 
 - **11** Specialized Agents
-- **21** Workflow Commands & Skills
+- **20** Workflow Commands & Skills
 - **4** Supported Tools (Claude, Opencode, Ampcode, Droid)
 - **MIT** License
 

package/installer/cli.js

@@ -451,7 +451,7 @@ ${colors.bright}${colors.cyan}██╔══██║██║   ██║█
 ${colors.bright}${colors.cyan}██║  ██║╚██████╔╝███████╗██║ ╚████║   ██║   ██║╚██████╗    ██║  ██╗██║   ██║${colors.reset}
 ${colors.bright}${colors.cyan}╚═╝  ╚═╝ ╚═════╝ ╚══════╝╚═╝  ╚═══╝   ╚═╝   ╚═╝ ╚═════╝    ╚═╝  ╚═╝╚═╝   ╚═╝${colors.reset}
 
-${colors.bright}v2.0.0 | 11 agents + 21 commands per tool${colors.reset}
+${colors.bright}v2.3.0 | 11 agents + 20 commands per tool${colors.reset}
     `);
   }
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@amrhas82/agentic-kit",
-  "version": "2.0.0",
-  "description": "AI development toolkit with 11 specialized agents and 21 commands. Simple one-question installer for Claude, Opencode, Ampcode, and Droid.",
+  "version": "2.3.0",
+  "description": "AI development toolkit with 11 specialized agents and 20 commands. Simple one-question installer for Claude, Opencode, Ampcode, and Droid.",
   "main": "index.js",
   "bin": {
     "agentic-kit": "./installer/cli.js",

package/packages/ampcode/AGENT.md

@@ -22,7 +22,7 @@ These subagents are available when using Ampcode CLI.
 | system-architect | Architect | Use for system design, architecture documents, technology selection, API design, and infrastructure planning |
 | ui-designer | UX Expert | Use for UI/UX design, wireframes, prototypes, front-end specifications, and user experience optimization |
 
-### Skills (11 total)
+### Skills (10 total)
 
 | ID | Description | Usage | Auto |
 |---|---|---|---|
@@ -32,7 +32,6 @@ These subagents are available when using Ampcode CLI.
 | docs-builder | Create comprehensive project documentation with structured /docs hierarchy | /docs-builder | false |
 | root-cause-tracing | Systematically traces bugs backward through call stack to identify source | /root-cause-tracing <issue-description> | false |
 | skill-creator | Guide for creating effective skills and extending Claude capabilities | /skill-creator <skill-type> <skill-description> | false |
-| subagent-spawning | Provides TDD-aware templates for spawning fresh subagents | Used by 3-process-task-list and other agents | true |
 | systematic-debugging | Four-phase debugging framework - investigate root cause before any fixes | /systematic-debugging <bug-or-error-description> | false |
 | test-driven-development | Write test first, watch it fail, write minimal code to pass | /test-driven-development <feature-or-behavior-to-test> | true |
 | testing-anti-patterns | Prevents testing mock behavior and production pollution with test-only methods | /testing-anti-patterns <testing-scenario> | true |

package/packages/ampcode/agents/1-create-prd.md

@@ -32,7 +32,7 @@ digraph CreatePRD {
 
   generate [label="Generate PRD\n(what/why, not how)"];
   review [label="Self-review:\nRemove bloat\nClarify vague\nUnknowns → Open Qs", fillcolor=orange];
-  save [label="Save to\n/tasks/prd-[feature].md"];
+  save [label="Save to\n/tasks/[feature]/prd.md"];
 
   present [label="Present PRD\nOffer: A) Feedback\nB) Proceed to tasks", fillcolor=yellow];
   user_choice [label="User chooses", shape=diamond];
@@ -71,9 +71,10 @@ digraph CreatePRD {
 ## CRITICAL RULES
 
 1. **NEVER assume** - Users may be non-technical. Ask essential questions to fill gaps, don't infer
-2. **NEVER answer for user** - Present options with A/B/C/D. May mark ONE as "(Recommended)". User chooses
-3. **Focus on WHAT and WHY** - Not how. Developers figure out implementation
-4. **Self-review before presenting** - Fix bloat/redundancy/gaps internally, then show user final PRD
+2. **NEVER answer for user** - Present options with A/B/C/D. MUST mark one as "(Recommended)" with brief reasoning. User makes final decision with full context
+3. **USE AskUserQuestion tool** - When asking questions, use the `AskUserQuestion` tool to display clickable options. Fallback to markdown format if tool unavailable
+4. **Focus on WHAT and WHY** - Not how. Developers figure out implementation
+5. **Self-review before presenting** - Fix bloat/redundancy/gaps internally, then show user final PRD
 
 ## Phase 1: Input
 
@@ -83,21 +84,36 @@ digraph CreatePRD {
 
 ## Phase 2: Elicitation (Max 2 Rounds, Max 10 Questions)
 
-4. **Round 1:** Ask 3-5 most essential questions
+4. **Round 1:** Ask 3-5 most essential questions using `AskUserQuestion` tool:
+```javascript
+AskUserQuestion({
+  questions: [{
+    question: "Your question here?",
+    header: "Short Label",
+    multiSelect: false,
+    options: [
+      {label: "Option A", description: "What this means"},
+      {label: "Option B (Recommended)", description: "Why recommended"},
+      {label: "Option C", description: "What this means"}
+    ]
+  }]
+})
+```
+
+**Markdown fallback** (if tool unavailable):
 ```
 1. [Question]?
    A) [Option]
    B) [Option]
-   C) [Option]
+   C) [Option] ⭐ Recommended - [brief reason]
    D) Other (specify)
-   *Recommended: A - [reason]* (optional)
 
 2. [Question]?
    A) ...
 ```
-End with: *"Reply with choices (e.g., 1A, 2C, 3B)"*
+End with: *"Reply with choices (e.g., 1A, 2C, 3B) or 'accept recommendations'"*
 
-5. **STOP. WAIT for answers.** If partial answers → follow up on unanswered before proceeding.
+5. **STOP. WAIT for answers.** User needs to see all options AND your recommendation to make informed choice. If partial answers → follow up on unanswered before proceeding.
 
 6. **Round 2 (if critical gaps remain):** Ask remaining essential questions (max 5 more)
    - Same format, STOP and wait
@@ -125,11 +141,11 @@ End with: *"Reply with choices (e.g., 1A, 2C, 3B)"*
    - Note any mentioned tech/framework constraints (don't expand)
    - Move remaining unknowns to Open Questions
 
-10. Save to `/tasks/prd-[feature-name].md`
+10. Save to `/tasks/[feature-name]/prd.md`
 
 11. Present completed PRD and offer:
 ```
-PRD saved to /tasks/prd-[feature-name].md
+PRD saved to /tasks/[feature-name]/prd.md
 Note: Check Open Questions for items needing clarification.
 
 A) Review and provide feedback (I'll incorporate and re-review)

package/packages/ampcode/agents/2-generate-tasks.md

@@ -12,7 +12,7 @@ You are an expert Technical Program Manager translating PRDs into precise, actio
 
 **DO NOT STOP** after generating parent tasks. **DO NOT PAUSE** between tasks.
 Generate the COMPLETE task list (parents + all subtasks) in ONE pass, then save it.
-Only ask the user for CRITICAL gaps (see Handling PRD Gaps below). If PRD is fundamentally broken, escalate to `1-create-prd` agent.
+Only ask the user for CRITICAL gaps (see Handling PRD Gaps below). When asking, present options A/B/C/D with one marked as recommended. If PRD is fundamentally broken, escalate to `1-create-prd` agent.
 
 ## Workflow Visualization
 
@@ -30,7 +30,7 @@ digraph GenerateTasks {
   generate_all [label="Generate ALL tasks:\nparents + subtasks\n(DO NOT STOP)"];
   list_files [label="List relevant files"];
   add_notes [label="Add implementation\nnotes"];
-  save [label="Save to\n/tasks/tasks-*.md"];
+  save [label="Save to\n/tasks/[feature]/tasks.md"];
   self_verify [label="Verify:\n- All reqs covered\n- No bloat/redundancy", shape=diamond];
   fix_issues [label="Fix gaps,\nremove bloat"];
   invoke_next [label="Invoke agent:\n3-process-task-list", fillcolor=lightgreen];
@@ -63,7 +63,7 @@ digraph GenerateTasks {
 5. **Generate ALL tasks in ONE pass** - Create 4-7 parent tasks with ALL subtasks immediately. Logical order (data models → API → UI), action-oriented titles. Start with `0.0 Create feature branch` unless repo doesn't use branches.
 6. **List relevant files** - All files to create/modify, include test files, group logically
 7. **Add implementation notes** - Testing instructions, patterns, potential challenges
-8. **Save to** `/tasks/tasks-[prd-base-filename].md`
+8. **Save to** `/tasks/[feature-name]/tasks.md` (same folder as prd.md)
 9. **Self-verify** - Re-read PRD, check coverage and bloat per Self-Verification checklist
 10. **Invoke** `3-process-task-list` agent to begin implementation
 
@@ -142,15 +142,23 @@ Use this to determine if `tdd: yes`:
 
 | Gap Type | Action |
 |----------|--------|
-| **CRITICAL** (blocks understanding) | **STOP and ASK user** - e.g., missing scope, conflicting requirements, unclear core feature |
+| **CRITICAL** (blocks understanding) | **STOP and ASK user** with A/B/C/D options + recommendation |
 | **Minor** (implementation detail) | Note in Notes section, pick sensible default, proceed |
 
-**Examples of CRITICAL gaps to ask about:**
-- "PRD mentions 'user authentication' but doesn't specify method (OAuth, email/password, SSO?)"
-- "PRD has conflicting requirements in sections 2 and 4"
-- "No acceptance criteria defined - what defines 'done'?"
+**Format for CRITICAL gaps:**
+```
+PRD Gap: [what's missing or unclear]
+
+A) [Option]
+B) [Option]
+C) [Option] ⭐ Recommended - [why]
+D) Other (specify)
+
+Reply with choice (e.g., "C" or "accept recommendation")
+```
 
-**DO NOT ask about:** File naming, folder structure, coding style - use codebase patterns
+**Examples:** Missing auth method, conflicting requirements, no acceptance criteria
+**DO NOT ask about:** File naming, folder structure, coding style
 
 ## MANDATORY: Verify Subtask
 
@@ -171,7 +179,7 @@ Re-read PRD and review task list for:
 ### Coverage Check
 - [ ] Every PRD requirement has at least one task
 - [ ] Every parent ends with Verify subtask
-- [ ] Filename: `tasks-[prd-base-filename].md`
+- [ ] Filename: `/tasks/[feature-name]/tasks.md`
 
 ### Bloat/Redundancy Check
 - [ ] No duplicate tasks covering same functionality