@amrhas82/agentic-kit 1.1.0 → 1.2.0

package/packages/ampcode/settings.json

@@ -0,0 +1,13 @@
+{
+  "amp.anthropic.thinking.enabled": true,
+  "amp.git.commit.ampThread.enabled": true,
+  "amp.git.commit.coauthor.enabled": true,
+  "amp.todos.enabled": true,
+  "amp.terminal.commands.nodeSpawn.loadProfile": "always",
+  "amp.tools.stopTimeout": 300,
+  "amp.updates.mode": "auto",
+  "amp.permissions": [],
+  "amp.tools.disable": [],
+  "amp.mcpServers": {},
+  "amp.mcpPermissions": []
+}

package/packages/ampcode/skills/README.md

@@ -0,0 +1,76 @@
+# Droid Slash Commands
+
+This directory contains 22 transformed Claude skills converted into Factory.ai CLI compatible Droid slash commands.
+
+## Command Reference by Category
+
+### Core Development Skills (7)
+*Code creation, testing, and development workflows*
+
+| Command | Purpose | Key Features |
+|---------|---------|--------------|
+| **algorithmic-art** | Create algorithmic art using p5.js with seeded randomness and interactive parameter exploration | Algorithmic philosophy creation, p5.js templates, generator patterns, interactive viewer creation |
+| **artifacts-builder** | Build elaborate multi-component HTML artifacts using React, TypeScript, Tailwind CSS, and shadcn/ui | React + TypeScript setup, shadcn/ui components, Parcel bundling, single HTML output |
+| **canvas-design** | Create beautiful visual art in PNG and PDF documents using design philosophy and minimal text | Design philosophy creation, visual expression, minimal text approach, craftsmanship principles |
+| **code-review** | Request structured code review to catch issues before they cascade | Mandatory review triggers, focus areas, feedback handling, workflow integration |
+| **test-driven-development** | Write test first, watch it fail, write minimal code to pass - ensures tests actually verify behavior | Red-green-refactor cycle, iron law of TDD, test quality standards, common patterns |
+| **testing-anti-patterns** | Avoid testing anti-patterns - never test mock behavior, add test-only methods, or mock without understanding | Mock behavior testing prevention, production code pollution avoidance, dependency understanding |
+| **skill-creator** | Guide for creating effective skills that extend Claude's capabilities with specialized knowledge | Skill anatomy, progressive disclosure, bundled resources, creation workflow |
+
+### Debugging & Quality (4)
+*Systematic debugging, quality assurance, and verification*
+
+| Command | Purpose | Key Features |
+|---------|---------|--------------|
+| **systematic-debugging** | Systematic four-phase debugging framework - investigate root cause before any fixes | Four-phase process (investigation, analysis, hypothesis, implementation), evidence-based debugging |
+| **root-cause-tracing** | Systematically trace bugs backward through call stack to find original trigger, never just fix symptoms | Backward tracing process, instrumentation techniques, multi-layer defense, test pollution detection |
+| **condition-based-waiting** | Replace arbitrary timeouts with condition polling to eliminate flaky tests from timing guesses | Wait-for-condition patterns, polling implementation, race condition elimination |
+| **verification-before-completion** | Evidence before claims - verify work completion with fresh verification commands | Iron law of verification, gate function, common failure patterns, evidence-based reporting |
+
+### Communication & Documentation (4)
+*Writing, collaboration, and documentation workflows*
+
+| Command | Purpose | Key Features |
+|---------|---------|--------------|
+| **brainstorming** | Turn rough ideas into fully-formed designs through collaborative questioning and exploration | Process-based questioning, approach exploration, design presentation, documentation workflow |
+| **internal-comms** | Write internal communications using company-approved formats and templates | 3P updates, company newsletters, FAQ responses, status reports, leadership communications |
+| **brand-guidelines** | Apply Anthropic's official brand colors and typography to any artifact | Official color palette (orange, blue, green, grays), Poppins/Lora fonts, CSS/Python implementations |
+| **mcp-builder** | Create high-quality MCP servers that enable LLMs to interact with external services through well-designed tools | MCP protocol, agent-centric design, workflow optimization, Python/Node implementations |
+
+### File Processing & Office Tools (4)
+*Document, presentation, and spreadsheet manipulation*
+
+| Command | Purpose | Key Features |
+|---------|---------|--------------|
+| **pdf** | Comprehensive PDF processing toolkit - extract text/tables, create PDFs, merge/split, handle forms | pypdf operations, form handling, image conversion, JavaScript pdf-lib, table extraction |
+| **docx** | Create, edit, and manipulate Word documents with JavaScript library and XML manipulation | docx library, raw XML editing, comments, tracked changes, validation schemas |
+| **pptx** | Create, edit, and analyze PowerPoint presentations with HTML conversion, XML manipulation, and design principles | Design-first approach, color palettes, HTML-to-PPTX conversion, XML structure access |
+| **xlsx** | Create, edit, and analyze spreadsheets with formulas, formatting, data analysis, and visualization | Formula requirements, pandas/openpyxl workflows, financial modeling standards, recalculation tools |
+
+### Web & API Integration (2)
+*Web application testing and API integration*
+
+| Command | Purpose | Key Features |
+|---------|---------|--------------|
+| **webapp-testing** | Test local web applications using Playwright - verify functionality, debug UI, capture screenshots | Playwright setup, server management, reconnaissance pattern, common testing patterns |
+| **theme-factory** | Apply professional themes to artifacts - 10 curated themes with color palettes and font pairings | 10 pre-built themes, theme showcase, custom theme creation, application standards |
+
+### Creative & Animation (1)
+*Animation and visual creativity*
+
+| Command | Purpose | Key Features |
+|---------|---------|--------------|
+| **slack-gif-creator** | Create animated GIFs optimized for Slack with size validation and composable animation primitives | Slack size constraints, validation tools, animation primitives (shake, bounce, spin, etc.), optimization strategies |
+
+## Usage
+
+Each command can be invoked in Droid with:
+```
+/command-name <optional-arguments>
+```
+
+Arguments should match the `argument-hint` specified in each command's YAML frontmatter.
+
+## Transformation Process
+
+These commands were transformed from Claude skills located in `~/.factory/commands/` according to Factory.ai CLI formatting requirements. Each skill was renamed from `SKILL.md` to `{skill-name}.md` and reformatted with proper YAML frontmatter for Droid compatibility.

package/packages/ampcode/subagents-and-skills.md

@@ -0,0 +1,79 @@
+# Agents and Skills Reference
+
+## Subagents Directory
+
+| Title | ID | When To Use |
+|---|---|---|
+| 1-Create PRD | 1-create-prd | Define scope with a Product Requirement Document (PRD) |
+| 2-Generate Tasks | 2-generate-tasks | Break down PRD into granular, actionable task list |
+| 3-Process Task List | 3-process-task-list | Guide AI to tackle tasks iteratively with review |
+| UX Expert | ux-expert | UI/UX design, wireframes, prototypes, front-end specs |
+| Scrum Master | scrum-master | Story creation, epic management, agile process guidance |
+| Test Architect & Quality Advisor | qa-test-architect | Test architecture review, quality gates, code improvement |
+| Product Owner | product-owner | Backlog management, story refinement, acceptance criteria |
+| Product Manager | product-manager | PRDs, product strategy, feature prioritization, roadmaps |
+| Full Stack Developer | full-stack-dev | Code implementation, debugging, refactoring |
+| Master Orchestrator | orchestrator | Workflow coordination, multi-agent tasks, role switching |
+| Master Task Executor | master | Comprehensive expertise across all domains |
+| Architect | holistic-architect | System design, architecture docs, API design |
+| Business Analyst | business-analyst | Market research, competitive analysis, project briefs |
+
+## Skills/Commands
+
+### Core Development Skills (7)
+*Code creation, testing, and development workflows*
+
+| Command | Purpose | Key Features |
+|---------|---------|--------------|
+| **algorithmic-art** | Create algorithmic art using p5.js with seeded randomness and interactive parameter exploration | Algorithmic philosophy creation, p5.js templates, generator patterns, interactive viewer creation |
+| **artifacts-builder** | Build elaborate multi-component HTML artifacts using React, TypeScript, Tailwind CSS, and shadcn/ui | React + TypeScript setup, shadcn/ui components, Parcel bundling, single HTML output |
+| **canvas-design** | Create beautiful visual art in PNG and PDF documents using design philosophy and minimal text | Design philosophy creation, visual expression, minimal text approach, craftsmanship principles |
+| **code-review** | Request structured code review to catch issues before they cascade | Mandatory review triggers, focus areas, feedback handling, workflow integration |
+| **test-driven-development** | Write test first, watch it fail, write minimal code to pass - ensures tests actually verify behavior | Red-green-refactor cycle, iron law of TDD, test quality standards, common patterns |
+| **testing-anti-patterns** | Avoid testing anti-patterns - never test mock behavior, add test-only methods, or mock without understanding | Mock behavior testing prevention, production code pollution avoidance, dependency understanding |
+| **skill-creator** | Guide for creating effective skills that extend Claude's capabilities with specialized knowledge | Skill anatomy, progressive disclosure, bundled resources, creation workflow |
+
+### Debugging & Quality (4)
+*Systematic debugging, quality assurance, and verification*
+
+| Command | Purpose | Key Features |
+|---------|---------|--------------|
+| **systematic-debugging** | Systematic four-phase debugging framework - investigate root cause before any fixes | Four-phase process (investigation, analysis, hypothesis, implementation), evidence-based debugging |
+| **root-cause-tracing** | Systematically trace bugs backward through call stack to find original trigger, never just fix symptoms | Backward tracing process, instrumentation techniques, multi-layer defense, test pollution detection |
+| **condition-based-waiting** | Replace arbitrary timeouts with condition polling to eliminate flaky tests from timing guesses | Wait-for-condition patterns, polling implementation, race condition elimination |
+| **verification-before-completion** | Evidence before claims - verify work completion with fresh verification commands | Iron law of verification, gate function, common failure patterns, evidence-based reporting |
+
+### Communication & Documentation (4)
+*Writing, collaboration, and documentation workflows*
+
+| Command | Purpose | Key Features |
+|---------|---------|--------------|
+| **brainstorming** | Turn rough ideas into fully-formed designs through collaborative questioning and exploration | Process-based questioning, approach exploration, design presentation, documentation workflow |
+| **internal-comms** | Write internal communications using company-approved formats and templates | 3P updates, company newsletters, FAQ responses, status reports, leadership communications |
+| **brand-guidelines** | Apply Anthropic's official brand colors and typography to any artifact | Official color palette (orange, blue, green, grays), Poppins/Lora fonts, CSS/Python implementations |
+| **mcp-builder** | Create high-quality MCP servers that enable LLMs to interact with external services through well-designed tools | MCP protocol, agent-centric design, workflow optimization, Python/Node implementations |
+
+### File Processing & Office Tools (4)
+*Document, presentation, and spreadsheet manipulation*
+
+| Command | Purpose | Key Features |
+|---------|---------|--------------|
+| **pdf** | Comprehensive PDF processing toolkit - extract text/tables, create PDFs, merge/split, handle forms | pypdf operations, form handling, image conversion, JavaScript pdf-lib, table extraction |
+| **docx** | Create, edit, and manipulate Word documents with JavaScript library and XML manipulation | docx library, raw XML editing, comments, tracked changes, validation schemas |
+| **pptx** | Create, edit, and analyze PowerPoint presentations with HTML conversion, XML manipulation, and design principles | Design-first approach, color palettes, HTML-to-PPTX conversion, XML structure access |
+| **xlsx** | Create, edit, and analyze spreadsheets with formulas, formatting, data analysis, and visualization | Formula requirements, pandas/openpyxl workflows, financial modeling standards, recalculation tools |
+
+### Web & API Integration (2)
+*Web application testing and API integration*
+
+| Command | Purpose | Key Features |
+|---------|---------|--------------|
+| **webapp-testing** | Test local web applications using Playwright - verify functionality, debug UI, capture screenshots | Playwright setup, server management, reconnaissance pattern, common testing patterns |
+| **theme-factory** | Apply professional themes to artifacts - 10 curated themes with color palettes and font pairings | 10 pre-built themes, theme showcase, custom theme creation, application standards |
+
+### Creative & Animation (1)
+*Animation and visual creativity*
+
+| Command | Purpose | Key Features |
+|---------|---------|--------------|
+| **slack-gif-creator** | Create animated GIFs optimized for Slack with size validation and composable animation primitives | Slack size constraints, validation tools, animation primitives (shake, bounce, spin, etc.), optimization strategies |

package/packages/ampcode/variants.json

@@ -0,0 +1,67 @@
+{
+  "lite": {
+    "name": "Lite",
+    "description": "Essential workflow agents with core document and debugging skills optimized for amplified development",
+    "useCase": "Users wanting comprehensive amplified workflow management with essential document processing and debugging capabilities",
+    "targetUsers": "Beginners, evaluators, developers wanting balanced features with amplified productivity",
+    "agents": [
+      "1-create-prd",
+      "2-generate-tasks",
+      "3-process-task-list",
+      "master"
+    ],
+    "skills": [
+      "docx",
+      "pdf",
+      "code-review",
+      "brainstorming",
+      "root-cause-tracing",
+      "mcp-builder",
+      "systematic-debugging"
+    ],
+    "resources": "*",
+    "hooks": "*"
+  },
+  "standard": {
+    "name": "Standard",
+    "description": "Complete workflow and development team with enhanced testing and validation skills for amplified development",
+    "useCase": "Professional accelerated development with full team coordination, testing, and comprehensive skill set",
+    "targetUsers": "Professional developers, teams focused on velocity, quality-focused users",
+    "agents": [
+      "1-create-prd",
+      "2-generate-tasks",
+      "3-process-task-list",
+      "master",
+      "orchestrator",
+      "qa-test-architect",
+      "full-stack-dev",
+      "business-analyst",
+      "ux-expert"
+    ],
+    "skills": [
+      "docx",
+      "pdf",
+      "code-review",
+      "brainstorming",
+      "root-cause-tracing",
+      "mcp-builder",
+      "webapp-testing",
+      "xlsx",
+      "systematic-debugging",
+      "verification-before-completion",
+      "skill-creator"
+    ],
+    "resources": "*",
+    "hooks": "*"
+  },
+  "pro": {
+    "name": "Pro",
+    "description": "Complete installation with all capabilities optimized for maximum amplified development and automation",
+    "useCase": "Full-featured installation for users needing all AI codegen, document processing, testing, and advanced automation capabilities",
+    "targetUsers": "Power users, enterprises, teams requiring maximum velocity, automation-focused developers",
+    "agents": "*",
+    "skills": "*",
+    "resources": "*",
+    "hooks": "*"
+  }
+}

package/packages/claude/AGENTS.md

@@ -0,0 +1,243 @@
+# Project Agents
+
+This file provides guidance and memory for your coding CLI.
+
+# Opencode subagents and Tasks (OpenCode)
+
+OpenCode reads AGENTS.md during initialization and uses it as part of its system prompt for the session. 
+
+## How To Use With Claude
+
+- Copy/paste `claude` subfolders in this project to ~/.claude and Claude will read and access agents from ~/.claude/agents and tasks from ~/.claude/tasks,
+- You can access agents using "@ux-expert", or you can reference a role naturally, e.g., "As ux-expert, implement ..." or use commands defined in your tasks.
+
+Note
+- Orchestrators run as mode: primary; other agents as all.
+- All agents have tools enabled: write, edit, bash.
+
+## Agents
+
+### Directory
+
+| Title | ID | When To Use |
+|---|---|---|
+| 1-Create PRD | 1-create-prd | 1. Define Scope: use to clearly outlining what needs to be built with a Product Requirement Document (PRD) |
+| 2-Generate Tasks | 2-generate-tasks | 2. Detailed Planning: use to break down the PRD into a granular, actionable task list |
+| 3-Process Task List | 3-process-task-list | 3. Iterative Implementation: use to guide the AI to tackle one task at a time, allowing you to review and approve each change |
+| UX Expert | ux-expert | Use for UI/UX design, wireframes, prototypes, front-end specifications, and user experience optimization |
+| Scrum Master | scrum-master | Use for story creation, epic management, retrospectives in party-mode, and agile process guidance |
+| Test Architect & Quality Advisor | qa-test-architect | Use for comprehensive test architecture review, quality gate decisions, and code improvement. Provides thorough analysis including requirements traceability, risk assessment, and test strategy. Advisory only - teams choose their quality bar. |
+| Product Owner | product-owner | Use for backlog management, story refinement, acceptance criteria, sprint planning, and prioritization decisions |
+| Product Manager | product-manager | Use for creating PRDs, product strategy, feature prioritization, roadmap planning, and stakeholder communication |
+| Full Stack Developer | full-stack-dev | Use for code implementation, debugging, refactoring, and development best practices |
+| Master Orchestrator | orchestrator | Use for workflow coordination, multi-agent tasks, role switching guidance, and when unsure which specialist to consult |
+| Master Task Executor | master | Use when you need comprehensive expertise across all domains, running 1 off tasks that do not require a persona, or just wanting to use the same agent for many things. |
+| Architect | holistic-architect | Use for system design, architecture documents, technology selection, API design, and infrastructure planning |
+| Business Analyst | business-analyst | Use for market research, brainstorming, competitive analysis, creating project briefs, initial project discovery, and documenting existing projects (brownfield) |
+
+
+### 1-Create PRD (id: 1-create-prd) 
+Source: [.agents/ux-expert.md](.agents/1-create-prd.md)
+
+- When to use: Define Scope: use to clearly outlining what needs to be built with a Product Requirement Document (PRD)  optimization
+- How to activate: Mention "create prd, ..." to get role-aligned behavior
+- Full definition: open the source file above (content not embedded)
+
+### 2-Generate Tasks (id: 2-generate-tasks) 
+Source: [.agents/ux-expert.md](.agents/2-generate-tasks.md)
+
+- When to use: 2. Detailed Planning: use to break down the PRD into a granular, actionable task list
+- How to activate: Mention "generate tasks, ..." to get role-aligned behavior
+- Full definition: open the source file above (content not embedded)
+
+### 3-Process Task List (id: 3-process-task-list)
+Source: [.agents/ux-expert.md](.agents/3-process-task-list.md)
+
+- When to use: 3. Iterative Implementation: use to guide the AI to tackle one task at a time, allowing you to review and approve each change
+- How to activate: Mention "process task list, ..." to get role-aligned behavior
+- Full definition: open the source file above (content not embedded)
+
+### UX Expert (id: ux-expert)
+Source: [.agents/ux-expert.md](.agents/ux-expert.md)
+
+- When to use: Use for UI/UX design, wireframes, prototypes, front-end specifications, and user experience optimization
+- How to activate: Mention "As ux-expert, ..." to get role-aligned behavior
+- Full definition: open the source file above (content not embedded)
+
+### Scrum Master (id: scrum-master)
+Source: [.agents/scrum-master.md](.agents/scrum-master.md)
+
+- When to use: Use for story creation, epic management, retrospectives in party-mode, and agile process guidance
+- How to activate: Mention "As scrum-master, ..." to get role-aligned behavior
+- Full definition: open the source file above (content not embedded)
+
+### Test Architect & Quality Advisor (id: qa-test-architect)
+Source: [.agents/qa-test-architect.md](.agents/qa-test-architect.md)
+
+- When to use: Use for comprehensive test architecture review, quality gate decisions, and code improvement. Provides thorough analysis including requirements traceability, risk assessment, and test strategy. Advisory only - teams choose their quality bar.
+- How to activate: Mention "As qa, ..." to get role-aligned behavior
+- Full definition: open the source file above (content not embedded)
+
+### Product Owner (id: product-owner)
+Source: [.agents/product-owner.md](.agents/product-owner.md)
+
+- When to use: Use for backlog management, story refinement, acceptance criteria, sprint planning, and prioritization decisions
+- How to activate: Mention "As product-owner, ..." to get role-aligned behavior
+- Full definition: open the source file above (content not embedded)
+
+### Product Manager (id: product-manager)
+Source: [.agents/product-manager.md](.agents/product-manager.md)
+
+- When to use: Use for creating PRDs, product strategy, feature prioritization, roadmap planning, and stakeholder communication
+- How to activate: Mention "As product-manager, ..." to get role-aligned behavior
+- Full definition: open the source file above (content not embedded)
+
+### Full Stack Developer (id: full-stack-dev)
+Source: [.agents/full-stack-dev.md](.agents/full-stack-dev.md)
+
+- When to use: Use for code implementation, debugging, refactoring, and development best practices
+- How to activate: Mention "As full-stack-dev, ..." to get role-aligned behavior
+- Full definition: open the source file above (content not embedded)
+
+### Master Orchestrator (id: orchestrator)
+Source: [.agents/orchestrator.md](.agents/orchestrator.md)
+
+- When to use: Use for workflow coordination, multi-agent tasks, role switching guidance, and when unsure which specialist to consult
+- How to activate: Mention "As orchestrator, ..." to get role-aligned behavior
+- Full definition: open the source file above (content not embedded)
+
+### Master Task Executor (id: master)
+Source: [.agents/master.md](.agents/master.md)
+
+- When to use: Use when you need comprehensive expertise across all domains, running 1 off tasks that do not require a persona, or just wanting to use the same agent for many things.
+- How to activate: Mention "As master, ..." to get role-aligned behavior
+- Full definition: open the source file above (content not embedded)
+
+### Architect (id: holistic-architect)
+Source: [.agents/holistic-architect.md](.agents/holistic-architect.md)
+
+- When to use: Use for system design, architecture documents, technology selection, API design, and infrastructure planning
+- How to activate: Mention "As architect, ..." to get role-aligned behavior
+- Full definition: open the source file above (content not embedded)
+
+### Business Analyst (id: business-analyst)
+Source: [.agents/business-analyst.md](.agents/business-analyst.md)
+
+- When to use: Use for market research, brainstorming, competitive analysis, creating project briefs, initial project discovery, and documenting existing projects (brownfield)
+- How to activate: Mention "As analyst, ..." to get role-aligned behavior
+- Full definition: open the source file above (content not embedded)
+
+## Tasks
+
+These are reusable task briefs; use the paths to open them as needed.
+
+### Task: validate-next-story
+Source: [../resources/task-briefs.md#validate-next-story](../resources/task-briefs.md#validate-next-story)
+- How to use: Reference the task in your prompt or execute via your configured commands.
+- Full brief: open the source file above (content not embedded)
+
+### Task: trace-requirements
+Source: [../resources/task-briefs.md#trace-requirements](../resources/task-briefs.md#trace-requirements)
+- How to use: Reference the task in your prompt or execute via your configured commands.
+- Full brief: open the source file above (content not embedded)
+
+### Task: test-design
+Source: [../resources/task-briefs.md#test-design](../resources/task-briefs.md#test-design)
+- How to use: Reference the task in your prompt or execute via your configured commands.
+- Full brief: open the source file above (content not embedded)
+
+### Task: shard-doc
+Source: [../resources/task-briefs.md#shard-doc](../resources/task-briefs.md#shard-doc)
+- How to use: Reference the task in your prompt or execute via your configured commands.
+- Full brief: open the source file above (content not embedded)
+
+### Task: risk-profile
+Source: [../resources/task-briefs.md#risk-profile](../resources/task-briefs.md#risk-profile)
+- How to use: Reference the task in your prompt or execute via your configured commands.
+- Full brief: open the source file above (content not embedded)
+
+### Task: review-story
+Source: [../resources/task-briefs.md#review-story](../resources/task-briefs.md#review-story)
+- How to use: Reference the task in your prompt or execute via your configured commands.
+- Full brief: open the source file above (content not embedded)
+
+### Task: qa-test-architect-gate
+Source: [../resources/task-briefs.md#qa-gate](../resources/task-briefs.md#qa-gate)
+- How to use: Reference the task in your prompt or execute via your configured commands.
+- Full brief: open the source file above (content not embedded)
+
+### Task: nfr-assess
+Source: [../resources/task-briefs.md#nfr-assess](../resources/task-briefs.md#nfr-assess)
+- How to use: Reference the task in your prompt or execute via your configured commands.
+- Full brief: open the source file above (content not embedded)
+
+### Task: index-docs
+Source: [../resources/task-briefs.md#index-docs](../resources/task-briefs.md#index-docs)
+- How to use: Reference the task in your prompt or execute via your configured commands.
+- Full brief: open the source file above (content not embedded)
+
+### Task: generate-ai-frontend-prompt
+Source: [../resources/task-briefs.md#generate-ai-frontend-prompt](../resources/task-briefs.md#generate-ai-frontend-prompt)
+- How to use: Reference the task in your prompt or execute via your configured commands.
+- Full brief: open the source file above (content not embedded)
+
+### Task: facilitate-brainstorming-session
+Source: [../resources/task-briefs.md#facilitate-brainstorming-session](../resources/task-briefs.md#facilitate-brainstorming-session)
+- How to use: Reference the task in your prompt or execute via your configured commands.
+- Full brief: open the source file above (content not embedded)
+
+### Task: execute-checklist
+Source: [../resources/task-briefs.md#execute-checklist](../resources/task-briefs.md#execute-checklist)
+- How to use: Reference the task in your prompt or execute via your configured commands.
+- Full brief: open the source file above (content not embedded)
+
+### Task: document-project
+Source: [../resources/task-briefs.md#document-project](../resources/task-briefs.md#document-project)
+- How to use: Reference the task in your prompt or execute via your configured commands.
+- Full brief: open the source file above (content not embedded)
+
+### Task: create-next-story
+Source: [../resources/task-briefs.md#create-next-story](../resources/task-briefs.md#create-next-story)
+- How to use: Reference the task in your prompt or execute via your configured commands.
+- Full brief: open the source file above (content not embedded)
+
+### Task: create-doc
+Source: [../resources/task-briefs.md#create-doc](../resources/task-briefs.md#create-doc)
+- How to use: Reference the task in your prompt or execute via your configured commands.
+- Full brief: open the source file above (content not embedded)
+
+### Task: create-deep-research-prompt
+Source: [../resources/task-briefs.md#create-deep-research-prompt](../resources/task-briefs.md#create-deep-research-prompt)
+- How to use: Reference the task in your prompt or execute via your configured commands.
+- Full brief: open the source file above (content not embedded)
+
+### Task: create-brownfield-story
+Source: [../resources/task-briefs.md#create-brownfield-story](../resources/task-briefs.md#create-brownfield-story)
+- How to use: Reference the task in your prompt or execute via your configured commands.
+- Full brief: open the source file above (content not embedded)
+
+### Task: correct-course
+Source: [../resources/task-briefs.md#correct-course](../resources/task-briefs.md#correct-course)
+- How to use: Reference the task in your prompt or execute via your configured commands.
+- Full brief: open the source file above (content not embedded)
+
+### Task: brownfield-create-story
+Source: [../resources/task-briefs.md#brownfield-create-story](../resources/task-briefs.md#brownfield-create-story)
+- How to use: Reference the task in your prompt or execute via your configured commands.
+- Full brief: open the source file above (content not embedded)
+
+### Task: brownfield-create-epic
+Source: [../resources/task-briefs.md#brownfield-create-epic](../resources/task-briefs.md#brownfield-create-epic)
+- How to use: Reference the task in your prompt or execute via your configured commands.
+- Full brief: open the source file above (content not embedded)
+
+### Task: apply-qa-fixes
+Source: [../resources/task-briefs.md#apply-qa-fixes](../resources/task-briefs.md#apply-qa-fixes)
+- How to use: Reference the task in your prompt or execute via your configured commands.
+- Full brief: open the source file above (content not embedded)
+
+### Task: advanced-elicitation
+Source: [../resources/task-briefs.md#advanced-elicitation](../resources/task-briefs.md#advanced-elicitation)
+- How to use: Reference the task in your prompt or execute via your configured commands.
+- Full brief: open the source file above (content not embedded)
+

package/packages/claude/README.md

@@ -0,0 +1,23 @@
+# Claude Code Packages
+
+Claude Code AI development assistant packages optimized for conversational AI interactions.
+
+## Structure
+- `lite/` - Minimal setup with 3 core agents
+- `standard/` - Full agent set with 8 core skills  
+- `pro/` - Complete toolkit with 14 advanced skills
+
+## Content Source
+Existing content available in `../claude_temp_backup/` ready to be organized into variants.
+
+## Optimization Focus
+- Conversational AI patterns
+- Markdown formatting
+- Claude-specific response handling
+- Plugin integration
+
+## Next Steps
+1. Copy 3 core agents to `lite/`
+2. Copy all agents + 8 skills to `standard/`
+3. Copy all agents + 14 skills to `pro/`
+4. Customize for Claude-specific optimizations

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

@@ -0,0 +1,56 @@
+---
+name: 1-create-prd
+description: Creates Product Requirements Documents (PRDs) through structured discovery. Use when user requests PRD creation, needs to document/formalize feature requirements, or provides a feature idea requiring structured documentation before implementation.
+model: inherit
+color: green
+---
+
+You are an expert Product Manager creating clear, actionable PRDs for junior developers.
+
+## Core Workflow
+1. **NEVER write PRD immediately** - Ask 5-10 clarifying questions first
+2. **Format questions with lettered/numbered options** (A/B/C or 1/2/3) for quick responses
+3. **Generate comprehensive PRD** following structure below
+4. **Save as** `/tasks/[n]-prd-[feature-name].md` (n = 0001, 0002, etc.)
+
+## Discovery Questions (Adapt based on context)
+- **Problem & Goals:** What problem does this solve? Primary goal? (Options: A) Increase engagement, B) Reduce friction, C) Add capability, D) Other)
+- **Target Users:** Who will use this? (Provide persona options)
+- **Core Functionality:** Key actions users should perform? (List with letters)
+- **User Stories:** Format: "As a [user], I want to [action] so that [benefit]"
+- **Acceptance Criteria:** How will we know it's successfully implemented?
+- **Testing & Verification:** What types of testing are needed to verify each user story is delivered? (Options: A) Unit tests, B) Integration tests, C) Manual qa-test-architect testing, D) End-to-end tests, E) Combination, F) Other)
+- **Scope & Boundaries:** What should this NOT do (non-goals)?
+- **Data Requirements:** What data is needed? (Provide type options)
+- **Design/UI:** Mockups available? Desired feel? (A) Minimal, B) Data-rich, C) Interactive, D) Other)
+- **Edge Cases:** Error conditions to consider? (Suggest common ones)
+
+## PRD Structure (Required sections)
+1. **Introduction/Overview** - Brief feature description, problem statement, high-level goal
+2. **Goals** - Specific, measurable objectives (bullet points)
+3. **User Stories** - Format: "As a [user], I want to [action] so that [benefit]" (multiple scenarios)
+4. **Functional Requirements** - Numbered, imperative language ("The system must..."), explicit, unambiguous
+5. **Non-Goals (Out of Scope)** - What is NOT included
+6. **Design Considerations** (Optional) - Mockups, UI/UX requirements, existing components
+7. **Technical Considerations** (Optional) - Constraints, dependencies, integration points, suggested approaches
+8. **Success Metrics** - Measurable indicators (engagement rates, error reduction, etc.)
+9. **Open Questions** - Remaining uncertainties
+
+## Writing Guidelines
+Write for junior developers: avoid jargon, be specific and concrete, focus on requirements not implementation, use examples when ambiguous, structure with headings/lists, maintain consistent terminology.
+
+## Critical Rules
+1. NEVER implement - only document
+2. ALWAYS ask clarifying questions first (5-10 questions)
+3. ALWAYS use letter/number options for easy responses
+4. Save as `/tasks/[n]-prd-[feature-name].md`
+5. Write for junior developers
+
+## Self-Verification Before Saving
+- [ ] Functional requirements numbered and specific
+- [ ] User stories follow format
+- [ ] Non-goals stated
+- [ ] Success metrics measurable
+- [ ] Language clear for junior developer
+- [ ] Correct filename in `/tasks/`
+- [ ] No implementation details (only requirements)

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

@@ -0,0 +1,73 @@
+---
+name: 2-generate-tasks
+description: Converts PRDs into actionable development task lists. Use when user requests "generate tasks from PRD [filename]", provides a PRD file path asking for implementation guidance, wants to "break down this PRD into tasks", or asks "what needs to be built" from a PRD. NOT for writing PRDs or general implementation without a PRD reference.
+model: inherit
+color: blue
+---
+
+You are an expert Technical Program Manager translating PRDs into precise, actionable task lists for junior developers, accounting for existing codebase patterns.
+
+## Two-Phase Process
+
+### Phase 1: High-Level Planning (STOP after this)
+1. **Read & validate PRD** - Confirm file exists, note filename for task list naming
+2. **Analyze PRD** - Extract requirements, user stories, acceptance criteria, dependencies, non-functional requirements
+3. **Assess codebase** - Review structure, patterns, conventions, testing framework, reusable components, similar features, file organization
+4. **Generate 4-7 parent tasks** - Logical order (data models → API → UI), action-oriented titles, align with PRD
+5. **Save to** `/tasks/tasks-[prd-base-filename].md`
+6. **Present parent tasks** - Say: "I have generated the high-level tasks based on the PRD. Ready to generate the sub-tasks? Respond with 'Go' to proceed."
+7. **STOP - Wait for "Go" confirmation** - Incorporate any requested changes first
+
+### Phase 2: Detailed Sub-Task Generation (After "Go")
+8. **Break down each parent task** - Sub-tasks: specific, actionable, 1-4 hours each, logical order, reference specific files, include testing, handle errors/edge cases/validation, consider accessibility/performance/security, leverage existing patterns
+9. **List relevant files** - All files to create/modify, include test files, brief descriptions, use project path conventions, group logically
+10. **Add implementation notes** - Testing instructions, architectural patterns, potential challenges, reference similar implementations
+11. **Generate final output** - Markdown format below, proper numbering (1.0, 1.1, 2.0...), checkbox formatting
+12. **Save and confirm** - Write to `/tasks/tasks-[prd-base-filename].md`, confirm completion
+
+## Output Format Requirements
+
+Your task list MUST follow this exact structure:
+
+```markdown
+## Relevant Files
+
+- `path/to/file1.ts` - Description of relevance and purpose
+- `path/to/file1.test.ts` - Unit tests for file1.ts
+- `path/to/file2.tsx` - Description of relevance and purpose
+- `path/to/file2.test.tsx` - Unit tests for file2.tsx
+
+### Notes
+
+- Testing instructions and framework details
+- Architectural guidance or patterns to follow
+- Important considerations or warnings
+
+## Tasks
+
+- [ ] 1.0 Parent Task Title
+  - [ ] 1.1 Specific sub-task with implementation details
+  - [ ] 1.2 Another sub-task with clear action items
+  - [ ] 1.3 Testing-related sub-task
+- [ ] 2.0 Second Parent Task Title
+  - [ ] 2.1 Sub-task description
+  - [ ] 2.2 Sub-task description
+```
+
+## Guidelines
+**Quality:** Clear for junior developers, complete (cover all PRD requirements), practical/achievable, leverage existing patterns, include testing, logical flow
+**Split task if:** Multiple files, different layers (UI/API/data), or >4 hours
+**Combine task if:** Would create artificial dependencies or over-granular steps
+**Parent tasks:** 5 ± 2 (adjust for complexity)
+**Test coverage:** Every component, utility, API endpoint needs test sub-tasks
+**Ambiguity:** Note in Notes section, provide default approach, flag for clarification, don't block
+**Writing:** Imperative mood ("Create", "Implement"), consistent PRD terminology, avoid jargon unless standard
+
+## Self-Verification Before Saving
+- [ ] All PRD requirements covered
+- [ ] Logical order with proper dependencies
+- [ ] Every implementation file has test file
+- [ ] Sub-tasks specific for junior developer
+- [ ] Filename: `tasks-[prd-base-filename].md`
+- [ ] Two-phase model followed (parent → wait → sub-tasks)
+- [ ] Existing codebase patterns referenced