@amrhas82/agentic-kit 1.5.0 → 1.7.5

package/packages/opencode/AGENTS.md

@@ -1,388 +1,55 @@
-# Global Opencode Agents
+# Global Opencode CLI
 
-This file provides guidance and memory for your coding CLI.
+Opencode is a lightweight CLI tool that provides workflow automation commands.
 
-# Opencode subagents and Tasks (OpenCode)
+## Opencode Subagents (Reference)
 
-Opencode reads AGENTS.md during initialization and uses it as part of its system prompt for the session. 
+These subagents are available when using Claude Code CLI. Opencode can reference them but doesn't implement them directly.
 
-## How To Use With Claude
+### Subagents (14 total)
 
-Activate agents by mentioning their ID in your prompts:
-- `"@qa-test-architect review this code"`
-- Copy/paste `opencode` subfolders in this project to ~/.config/opencode and Opencode will read and access agents from ~/.config/opencode/agent and tasks from ~~/.config/opencode/resources/tasks-bried.md,
-- 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/master run as mode: primary; other agents as mode: subagents.
-- All agents have enbaled tools: write, edit, bash.
-
-## Agents
-
-### Directory
-
-| Title | ID | When To Use |
+| ID | Title | 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) |
-| Context Initializer | context-initializer | Use to initialize Opencode context for new/existing projects, discover and organize documentation, create AGENT.md and KNOWLEDGE_BASE.md for optimal token-efficient memory |
-
-### 1-Create PRD (id: 1-create-prd) 
-Source: [./agent/ux-expert.md](./agent/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: [./agent/ux-expert.md](./agent/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: [./agent/ux-expert.md](./agent/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: [./agent/ux-expert.md](./agent/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: [./agent/scrum-master.md](./agent/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: [./agent/qa-test-architect.md](./agent/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: [./agent/product-owner.md](./agent/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: [./agent/product-manager.md](./agent/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: [./agent/full-stack-dev.md](./agent/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: [./agent/orchestrator.md](./agent/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: [./agent/master.md](./agent/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: [./agent/holistic-architect.md](./agent/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)
-
-### Context Initializer (id: context-initializer)
-Source: [./agent/context-initializer.md](./agent/context-initializer.md)
-
-- When to use: Use to initialize Claude Code context for new/existing projects, discover and organize documentation, create CLAUDE.md and KNOWLEDGE_BASE.md for optimal token-efficient memory
-- How to activate: Mention "@context-initializer" or "As context-initializer, ..." to get role-aligned behavior
-- Full definition: open the source file above (content not embedded)
-
-### Business Analyst (id: business-analyst)
-Source: [./agent/business-analyst.md](./agent/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)
-
-## Commands
-
-These are slash commands available in the TUI. Use /command-name to execute.
-
-### Command: xlsx
-Source: [./command/xlsx.md](./command/xlsx.md)
-- Description: Create, edit, and analyze spreadsheets with formulas, formatting, data analysis, and visualization
-- Usage: `/xlsx <operation> <spreadsheet-file>`
-- Full definition: open the source file above (content not embedded)
-
-### Command: webapp-testing
-Source: [./command/webapp-testing.md](./command/webapp-testing.md)
-- Description: Test local web applications using Playwright - verify functionality, debug UI, capture screenshots
-- Usage: `/webapp-testing <webapp-url-or-local-server>`
-- Full definition: open the source file above (content not embedded)
-
-### Command: systematic-debugging
-Source: [./command/systematic-debugging.md](./command/systematic-debugging.md)
-- Description: Systematic four-phase debugging framework - investigate root cause before any fixes
-- Usage: `/systematic-debugging <bug-or-error-description>`
-- Full definition: open the source file above (content not embedded)
-
-### Command: slack-gif-creator
-Source: [./command/slack-gif-creator.md](./command/slack-gif-creator.md)
-- Description: Create animated GIFs optimized for Slack with size validation and composable animation primitives
-- Usage: `/slack-gif-creator <gif-type> <animation-concept>`
-- Full definition: open the source file above (content not embedded)
-
-### Command: verification-before-completion
-Source: [./command/verification-before-completion.md](./command/verification-before-completion.md)
-- Description: Verify work meets requirements before marking complete - prevents incomplete deliverables
-- Usage: `/verification-before-completion <work-to-verify>`
-- Full definition: open the source file above (content not embedded)
-
-### Command: skill-creator
-Source: [./command/skill-creator.md](./command/command/skill-creator.md)
-- Description: Create reusable skills with proper structure, validation, and documentation
-- Usage: `/skill-creator <skill-type> <skill-description>`
-- Full definition: open the source file above (content not embedded)
-
-### Command: test-driven-development
-Source: [./command/test-driven-development.md](./command/test-driven-development.md)
-- Description: Write test first, watch it fail, write minimal code to pass - ensures tests actually verify behavior
-- Usage: `/test-driven-development <feature-or-behavior-to-test>`
-- Full definition: open the source file above (content not embedded)
-
-### Command: testing-anti-patterns
-Source: [./command/testing-anti-patterns.md](./command/testing-anti-patterns.md)
-- Description: Identify and avoid common testing anti-patterns that create fragile, useless tests
-- Usage: `/testing-anti-patterns <testing-scenario>`
-- Full definition: open the source file above (content not embedded)
-
-### Command: theme-factory
-Source: [./command/theme-factory.md](./command/theme-factory.md)
-- Description: Generate consistent themes with proper color systems, typography, and spacing
-- Usage: `/theme-factory <theme-type> <design-requirements>`
-- Full definition: open the source file above (content not embedded)
-
-### Command: root-cause-tracing
-Source: [./command/root-cause-tracing.md](./command/root-cause-tracing.md)
-- Description: Trace issues to their root cause using systematic investigation techniques
-- Usage: `/root-cause-tracing <issue-description>`
-- Full definition: open the source file above (content not embedded)
-
-### Command: internal-comms
-Source: [./command/internal-comms.md](./command/internal-comms.md)
-- Description: Structure internal communications for clarity, actionability, and team alignment
-- Usage: `/internal-comms <communication-type> <audience>`
-- Full definition: open the source file above (content not embedded)
-
-### Command: pdf
-Source: [./command/pdf.md](./command/pdf.md)
-- Description: Create, edit, and analyze PDF documents with proper formatting and structure
-- Usage: `/pdf <operation> <pdf-file>`
-- Full definition: open the source file above (content not embedded)
-
-### Command: mcp-builder
-Source: [./command/mcp-builder.md](./command/mcp-builder.md)
-- Description: Build Model Context Protocol servers with proper tool definitions and error handling
-- Usage: `/mcp-builder <server-type> <specifications>`
-- Full definition: open the source file above (content not embedded)
-
-### Command: condition-based-waiting
-Source: [./command/condition-based-waiting.md](./command/condition-based-waiting.md)
-- Description: Implement robust waiting mechanisms based on conditions rather than fixed delays
-- Usage: `/condition-based-waiting <condition-type> <timeout-specs>`
-- Full definition: open the source file above (content not embedded)
-
-### Command: pptx
-Source: [./command/pptx.md](./command/pptx.md)
-- Description: Create professional PowerPoint presentations with proper structure and design
-- Usage: `/pptx <presentation-type> <content-outline>`
-- Full definition: open the source file above (content not embedded)
-
-### Command: docx
-Source: [./command/docx.md](./command/docx.md)
-- Description: Create and edit Word documents with proper formatting and structure
-- Usage: `/docx <operation> <document-specs>`
-- Full definition: open the source file above (content not embedded)
-
-### Command: brand-guidelines
-Source: [./command/brand-guidelines.md](./command/brand-guidelines.md)
-- Description: Establish comprehensive brand guidelines with visual identity and usage rules
-- Usage: `/brand-guidelines <brand-type> <requirements>`
-- Full definition: open the source file above (content not embedded)
-
-### Command: brainstorming
-Source: [./command/brainstorming.md](./command/brainstorming.md)
-- Description: Facilitate structured brainstorming sessions with proven techniques and frameworks
-- Usage: `/brainstorming <session-type> <topic>`
-- Full definition: open the source file above (content not embedded)
-
-### Command: canvas-design
-Source: [./command/canvas-design.md](./command/canvas-design.md)
-- Description: Design visual canvases for business models, user journeys, and strategic planning
-- Usage: `/canvas-design <canvas-type> <design-goals>`
-- Full definition: open the source file above (content not embedded)
-
-### Command: artifacts-builder
-Source: [./command/artifacts-builder.md](./command/artifacts-builder.md)
-- Description: Build structured artifacts with proper validation, formatting, and documentation
-- Usage: `/artifacts-builder <artifact-type> <specifications>`
-- Full definition: open the source file above (content not embedded)
-
-### Command: algorithmic-art
-Source: [./command/algorithmic-art.md](./command/algorithmic-art.md)
-- Description: Generate algorithmic art with mathematical patterns and aesthetic principles
-- Usage: `/algorithmic-art <art-type> <pattern-specs>`
-- Full definition: open the source file above (content not embedded)
-
-### Command: code-review
-Source: [./command/code-review.md](./command/code-review.md)
-- Description: Conduct thorough code reviews with focus on quality, security, and maintainability
-- Usage: `/code-review <review-scope> <focus-areas>`
-- Full definition: open the source file above (content not embedded)
-
+| 1-create-prd | 1-Create PRD | Define Scope - use to clearly outline what needs to be built with a Product Requirement Document (PRD) |
+| 2-generate-tasks | 2-Generate Tasks | Detailed Planning - use to break down the PRD into a granular, actionable task list |
+| 3-process-task-list | 3-Process Task List | Iterative Implementation - use to guide the AI to tackle one task at a time, allowing you to review and approve each change |
+| backlog-manager | Product Owner | Use for backlog management, story refinement, acceptance criteria, sprint planning, and prioritization decisions |
+| code-developer | Full Stack Developer | Use for code implementation, debugging, refactoring, and development best practices |
+| context-builder | Context Initializer | Use to initialize Claude Code context for new/existing projects, discover and organize documentation, create CLAUDE.md and KNOWLEDGE_BASE.md for optimal token-efficient memory |
+| feature-planner | Product Manager | Use for creating PRDs, product strategy, feature prioritization, roadmap planning, and stakeholder communication |
+| market-researcher | Business Analyst | Use for market research, brainstorming, competitive analysis, creating project briefs, initial project discovery, and documenting existing projects (brownfield) |
+| master | Master Task Executor | 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 |
+| orchestrator | Master Orchestrator | Use for workflow coordination, multi-agent tasks, role switching guidance, and when unsure which specialist to consult |
+| quality-assurance | Test Architect & Quality Advisor | 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 |
+| story-writer | Scrum Master | Use for story creation, epic management, retrospectives in party-mode, and agile process guidance |
+| 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 |
+
+## Opencode Commands (20 total)
+
+| ID | Description | Usage | Auto |
+|---|---|---|---|
+| brainstorming | Refines rough ideas into fully-formed designs through collaborative questioning | /brainstorming <session-type> <topic> | false |
+| code-review | Reviews implementation against plan or requirements before proceeding | /code-review <review-scope> <focus-areas> | false |
+| condition-based-waiting | Replaces arbitrary timeouts with condition polling to wait for actual state changes | /condition-based-waiting <condition-type> <timeout-specs> | false |
+| debug | Debug an issue systematically using structured investigation techniques | /debug <issue-description> | - |
+| docs-builder | Create comprehensive project documentation with structured /docs hierarchy | /docs-builder | false |
+| explain | Explain code for someone new to the codebase | /explain <code-section> | - |
+| git-commit | Analyze changes and create intelligent git commits | /git-commit | - |
+| optimize | Analyze and optimize performance issues | /optimize <target-area> | - |
+| refactor | Refactor code while maintaining behavior and tests | /refactor <code-section> | - |
+| review | Comprehensive code review including quality, tests, and architecture | /review | - |
+| root-cause-tracing | Systematically traces bugs backward through call stack to identify source | /root-cause-tracing <issue-description> | false |
+| security | Security vulnerability scan and analysis | /security | - |
+| ship | Pre-deployment verification checklist | /ship | - |
+| 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 |
+| test-generate | Generate comprehensive test suites for existing code | /test-generate <code-section> | - |
+| testing-anti-patterns | Prevents testing mock behavior and production pollution with test-only methods | /testing-anti-patterns <testing-scenario> | true |
+| verification-before-completion | Requires running verification commands before making any success claims | /verification-before-completion <work-to-verify> | true |
+
+All resources are auto-discovered from frontmatter in their respective directories:
+- **Agents**: `./agent/*.md`
+- **Commands**: `./command/*.md`

package/packages/opencode/agent/1-create-prd.md

@@ -1,6 +1,7 @@
 ---
 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.
+description: Create PRDs through structured discovery
+when_to_use: Define Scope - use to clearly outline what needs to be built with a Product Requirement Document (PRD)
 mode: subagent
 temperature: 0.4
 tools:
@@ -11,51 +12,79 @@ tools:
 
 You are an expert Product Manager creating clear, actionable PRDs for junior developers.
 
+## Workflow Visualization
+
+```dot
+digraph CreatePRD {
+  rankdir=TB;
+  node [shape=box, style=filled, fillcolor=lightblue];
+
+  start [label="START", fillcolor=lightgreen];
+  context_given [label="Context provided\nby user?", shape=diamond];
+  read_context [label="READ context file\nQuote relevant parts"];
+  analyze [label="Analyze request"];
+  ask_questions [label="Ask 3-5 clarifying\nquestions (A/B/C format)", fillcolor=yellow];
+  wait_answers [label="WAIT for answers\n(MANDATORY STOP)", fillcolor=red];
+  generate_prd [label="Generate PRD\nfollowing structure"];
+  self_verify [label="Self-verify checklist", shape=diamond];
+  fix_issues [label="Fix missing items"];
+  save [label="Save to\n/tasks/[n]-prd-*.md"];
+  verify_file [label="Verify: file exists\n& has all sections", fillcolor=orange];
+  invoke_next [label="Invoke agent:\n2-generate-tasks", fillcolor=lightgreen];
+  done [label="DONE", fillcolor=lightgreen];
+
+  start -> context_given;
+  context_given -> read_context [label="YES"];
+  context_given -> analyze [label="NO"];
+  read_context -> analyze;
+  analyze -> ask_questions;
+  ask_questions -> wait_answers;
+  wait_answers -> generate_prd [label="After user responds"];
+  generate_prd -> self_verify;
+  self_verify -> fix_issues [label="Issues found"];
+  self_verify -> save [label="All verified"];
+  fix_issues -> self_verify;
+  save -> verify_file;
+  verify_file -> invoke_next;
+  invoke_next -> done;
+}
+```
+
 ## 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.)
-5. **Agents** (../AGENTS.md): After saving the PRD to `/tasks/[n]-prd-[feature-name].md`, invoke the `2-generate-tasks` agent to process the PRD output and generate a granular, actionable task list for implementation.
-
-## 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]"
+
+1. **Read provided context** - If user gave a file, READ IT and quote relevant parts
+2. **Ask 3-5 clarifying questions** - Use lettered options (A/B/C) for quick responses
+3. **Wait for answers** - You are NOT allowed to write the PRD until user answers
+4. **Generate PRD** following structure below
+5. **Save to** `/tasks/[n]-prd-[feature-name].md` (n = 0001, 0002, etc.)
+6. **Invoke** `2-generate-tasks` agent to create task list from PRD
+
+## Discovery Questions (Pick 3-5 based on context)
+- **Problem & Goals:** What problem does this solve? Primary goal?
+- **Target Users:** Who will use this?
+- **Core Functionality:** Key actions users should perform?
+- **User Stories:** "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
+- **Edge Cases:** Error conditions to consider?
+
+## PRD Structure
+1. **Introduction/Overview** - Brief description, problem statement, high-level goal
+2. **Goals** - Specific, measurable objectives
+3. **User Stories** - "As a [user], I want to [action] so that [benefit]"
+4. **Functional Requirements** - Numbered, imperative ("The system must...")
 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.)
+6. **Design Considerations** (Optional) - Mockups, UI/UX requirements
+7. **Technical Considerations** (Optional) - Constraints, dependencies
+8. **Success Metrics** - Measurable indicators
 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
+Write for junior developers: avoid jargon, be specific, focus on requirements not implementation, use examples when ambiguous.
 
 ## 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)
+- [ ] Did I ask questions and wait for answers? (If no, STOP)
+- [ ] Did I read/quote any provided context?
+- [ ] Saving to correct path: `/tasks/[n]-prd-[feature-name].md`?
+- [ ] Functional requirements numbered and specific?
+- [ ] Non-goals stated?