super-opencode 1.1.2 → 1.2.0

package/.opencode/commands/soc-pm.md

@@ -5,9 +5,11 @@ description: Project management and orchestration
 # /soc-pm
 
 ## 1. Command Overview
+
 The `/soc-pm` command is the "Orchestrator." It manages the high-level state of the project. It uses the PDCA (Plan-Do-Check-Act) cycle to break down complex goals into `tasks`, track progress, and unblock other agents. It is the owner of `task.md`.
 
 ## 2. Triggers & Routing
+
 The command is the primary interface for the `pm-agent`.
 
 | Trigger Scenario | Flag | Target Agent | Action |
@@ -17,34 +19,41 @@ The command is the primary interface for the `pm-agent`.
 | **Verify Work** | `review` | `[pm-agent]` | Check deliverables |
 
 ## 3. Usage & Arguments
+
 ```bash
 /soc-pm [action] [target] [flags]
 ```
 
 ### Arguments
--   **`[action]`**: `plan`, `status`, `review`, `checkpoint`.
--   **`[target]`**: (Optional) Specific feature or milestone.
+
+- **`[action]`**: `plan`, `status`, `review`, `checkpoint`.
+- **`[target]`**: (Optional) Specific feature or milestone.
 
 ### Flags
--   **`--detail`**: Show full task history.
+
+- **`--detail`**: Show full task history.
 
 ## 4. Behavioral Flow (Orchestration)
 
 ### Phase 1: Plan (The Roadmap)
-1.  **Analyze**: Read User Request -> Break into Epics/Stories.
-2.  **Document**: updates `task.md` with checkboxes `[ ]`.
+
+1. **Analyze**: Read User Request -> Break into Epics/Stories.
+2. **Document**: updates `task.md` with checkboxes `[ ]`.
 
 ### Phase 2: Do (Tracking)
--   Monitors tool usage.
--   Updates task status to `[/]` (In Progress) or `[x]` (Done).
+
+- Monitors tool usage.
+- Updates task status to `[/]` (In Progress) or `[x]` (Done).
 
 ### Phase 3: Check (The Audit)
--   **Review**: Did we meet the acceptance criteria?
--   **Reflect**: Use `reflexion` skill if blocked.
+
+- **Review**: Did we meet the acceptance criteria?
+- **Reflect**: Use `reflexion` skill if blocked.
 
 ## 5. Output Guidelines (The Contract)
 
 ### Project Status Report
+
 ```markdown
 ## Project Status: [Phase]
 
@@ -64,36 +73,49 @@ The command is the primary interface for the `pm-agent`.
 ## 6. Examples
 
 ### A. Initial Planning
+
 ```bash
 /soc-pm plan "Build User Dashboard"
 ```
+
 *Effect:* Creates `task.md` with breakdown: "Design UI", "Setup API", "Integrate Frontend".
 
 ### B. Status Update
+
 ```bash
 /soc-pm status
 ```
+
 *Effect:* Reads current state and summarizes what has been done vs what is left.
 
 ## 7. Dependencies & Capabilities
 
 ### Agents
--   **PM Agent**: `@[.opencode/agents/pm-agent.md]` - Self-referential.
--   **All Agents**: Delegates work to them.
+
+- **PM Agent**: `@[.opencode/agents/pm-agent.md]` - Self-referential.
+- **All Agents**: Delegates work to them.
 
 ### Skills
--   **Reflexion**: `@[.opencode/skills/reflexion/SKILL.md]` - For unblocking the team.
+
+- **Reflexion**: `@[.opencode/skills/reflexion/SKILL.md]` - For unblocking the team.
 
 ### MCP Integration
--   **`filesystem`**: Managing `task.md` and `implementation_plan.md`.
+
+- **`filesystem`**: Managing `task.md` and `implementation_plan.md`.
 
 ## 8. Boundaries
 
 **Will:**
--   Manage `task.md`.
--   Delegate tasks to other agents.
--   Track overall progress.
+
+- Manage `task.md`.
+- Delegate tasks to other agents.
+- Track overall progress.
 
 **Will Not:**
--   **Write Code**: It manages those who write code.
--   **Solve Technical Bugs**: It assigns `[backend]` or `[quality]` to solve them.
+
+- **Write Code**: It manages those who write code.
+- **Solve Technical Bugs**: It assigns `[backend]` or `[quality]` to solve them.
+
+## User Instruction
+
+The user have executed the `/soc-pm` command by parsing the user's arguments provided in `<user-instruction>$ARGUMENTS</user-instruction>`, then perform the specified action (plan, status, review, or checkpoint) on the given target (or entire project if none specified), delegate to the pm-agent to manage the `task.md` file through the PDCA cycle—breaking down requests into epics and stories when planning, monitoring progress and updating task statuses during tracking, and verifying deliverables against acceptance criteria when reviewing—and generate a comprehensive project status report showing completed tasks, current focus areas, and any blockers.

package/.opencode/commands/soc-research.md

@@ -5,9 +5,11 @@ description: Deep web research and documentation lookup
 # /soc-research
 
 ## 1. Command Overview
+
 The `/soc-research` command is the "Archive." It scours the web and internal docs to find definitive truth. It operates on the "Cite or Die" principle: every claim must optionally be backed by a source. It does not hallucinate; it verifies.
 
 ## 2. Triggers & Routing
+
 The command routes to the `researcher` agent.
 
 | Trigger Scenario | Flag | Target Agent | Tool Used |
@@ -17,35 +19,42 @@ The command routes to the `researcher` agent.
 | **Deep Dive** | `--depth deep` | `[researcher]` | Recursive Search |
 
 ## 3. Usage & Arguments
+
 ```bash
 /soc-research [topic] [flags]
 ```
 
 ### Arguments
--   **`[topic]`**: The question or technology to investigate.
+
+- **`[topic]`**: The question or technology to investigate.
 
 ### Flags
--   **`--depth [quick|standard|deep]`**: (Default: `standard`).
--   **`--domain [url]`**: Restrict search to specific site (e.g., `github.com`).
+
+- **`--depth [quick|standard|deep]`**: (Default: `standard`).
+- **`--domain [url]`**: Restrict search to specific site (e.g., `github.com`).
 
 ## 4. Behavioral Flow (Orchestration)
 
 ### Phase 1: Parsing
-1.  **Decompose**: Break query into keywords.
-2.  **Select**: Choose tool (`tavily` for web, `context7` for docs).
+
+1. **Decompose**: Break query into keywords.
+2. **Select**: Choose tool (`tavily` for web, `context7` for docs).
 
 ### Phase 2: Execution (The Hunt)
--   **Broad Search**: Find candidate URLs.
--   **Deep Read**: Scrape content.
--   **Synthesize**: Cross-reference facts to find consensus.
+
+- **Broad Search**: Find candidate URLs.
+- **Deep Read**: Scrape content.
+- **Synthesize**: Cross-reference facts to find consensus.
 
 ### Phase 3: Reporting
--   Construct "Review of Literature."
--   Flag conflicting info ("Source A says X, Source B says Y").
+
+- Construct "Review of Literature."
+- Flag conflicting info ("Source A says X, Source B says Y").
 
 ## 5. Output Guidelines (The Contract)
 
 ### Research Report
+
 ```markdown
 ## Research: [Topic]
 
@@ -64,7 +73,9 @@ const x = new Library();
 ```
 
 ### Conflicting Info
--   StackOverflow suggests X, but Official Docs say Y (Deprecated).
+
+- StackOverflow suggests X, but Official Docs say Y (Deprecated).
+
 ```
 
 ## 6. Examples
@@ -73,33 +84,45 @@ const x = new Library();
 ```bash
 /soc-research "Best React form library 2025" --depth deep
 ```
+
 *Effect:* Compares React Hook Form vs TanStack Form based on bundle size and weekly downloads.
 
 ### B. Bug Hunting
+
 ```bash
 /soc-research "Prisma error P2002" --domain github.com
 ```
+
 *Effect:* Finds specific GitHub issues related to Unique Constraint violations.
 
 ## 7. Dependencies & Capabilities
 
 ### Agents
--   **Researcher**: `@[.opencode/agents/researcher.md]` - Primary persona.
+
+- **Researcher**: `@[.opencode/agents/researcher.md]` - Primary persona.
 
 ### Skills
--   **Sequential Thinking**: `@[.opencode/skills/sequential-thinking/SKILL.md]` - For resolving conflicts.
+
+- **Sequential Thinking**: `@[.opencode/skills/sequential-thinking/SKILL.md]` - For resolving conflicts.
 
 ### MCP Integration
--   **`tavily`**: Real-time web search.
--   **`context7`**: Documentation retrieval.
+
+- **`tavily`**: Real-time web search.
+- **`context7`**: Documentation retrieval.
 
 ## 8. Boundaries
 
 **Will:**
--   Find official documentation.
--   Summarize community consensus.
--   Provide direct links.
+
+- Find official documentation.
+- Summarize community consensus.
+- Provide direct links.
 
 **Will Not:**
--   **Execute Info**: It finds the code, but does not run it.
--   **Make Decisions**: It informs decisions, but `architect` decides.
+
+- **Execute Info**: It finds the code, but does not run it.
+- **Make Decisions**: It informs decisions, but `architect` decides.
+
+## User Instruction
+
+The user have executed the `/soc-research` command by parsing the user's arguments provided in `<user-instruction>$ARGUMENTS</user-instruction>`, then route to the researcher agent to investigate the specified topic, selecting the appropriate research depth (quick, standard, or deep) and tools (tavily for web search, context7 for documentation) based on flags and topic type, decompose the query into searchable keywords, gather information from multiple sources while cross-referencing facts to find consensus, and synthesize findings into a comprehensive research report with cited sources, key findings, code patterns, and flagging of any conflicting information.

package/.opencode/commands/soc-review.md

@@ -5,9 +5,11 @@ description: Code review and quality assessment
 # /soc-review
 
 ## 1. Command Overview
+
 The `/soc-review` command is the "Critic." It acts as a second pair of eyes before code is merged. It checks for logic errors, security vulnerabilities (OWASP), and adherence to the "Intentional Minimalism" design philosophy.
 
 ## 2. Triggers & Routing
+
 The command routes to specialized reviewers.
 
 | Trigger Scenario | Flag | Target Agent | Focus |
@@ -17,35 +19,42 @@ The command routes to specialized reviewers.
 | **Style/Lint** | `--quick` | `[reviewer]` | Formatting, Naming |
 
 ## 3. Usage & Arguments
+
 ```bash
 /soc-review [target] [flags]
 ```
 
 ### Arguments
--   **`[target]`**: File, directory, or Pull Request ID to review.
+
+- **`[target]`**: File, directory, or Pull Request ID to review.
 
 ### Flags
--   **`--scope [full|quick]`**: (Default: `full`).
--   **`--security`**: Triggers explicit security scan protocol.
+
+- **`--scope [full|quick]`**: (Default: `full`).
+- **`--security`**: Triggers explicit security scan protocol.
 
 ## 4. Behavioral Flow (Orchestration)
 
 ### Phase 1: Context Loading
-1.  **Read**: Load the target code.
-2.  **Context**: Load `implementation_plan.md` (to see what was intended).
+
+1. **Read**: Load the target code.
+2. **Context**: Load `implementation_plan.md` (to see what was intended).
 
 ### Phase 2: Analysis (The Audit)
--   **Static Analysis**: Grep for "smells" (`any`, `eval`, `console.log`).
--   **Logic Check**: Trace variable data flow.
--   **Design Check**: Does it match the Project Persona (Minimalism)?
+
+- **Static Analysis**: Grep for "smells" (`any`, `eval`, `console.log`).
+- **Logic Check**: Trace variable data flow.
+- **Design Check**: Does it match the Project Persona (Minimalism)?
 
 ### Phase 3: Reporting
--   Categorize findings by Severity (Critical, Warning, Info).
--   Reject if Critical issues exist.
+
+- Categorize findings by Severity (Critical, Warning, Info).
+- Reject if Critical issues exist.
 
 ## 5. Output Guidelines (The Contract)
 
 ### Code Review
+
 ```markdown
 ## Review: [Target]
 
@@ -70,33 +79,45 @@ Solid logic, but the SQL injection must be fixed before merge.
 ## 6. Examples
 
 ### A. Pre-Merge Review
+
 ```bash
 /soc-review src/features/payments --security
 ```
+
 *Effect:* Triggers `security` agent to specifically look for PCI compliance issues and raw secrets.
 
 ### B. Quick Sanity Check
+
 ```bash
 /soc-review --quick
 ```
+
 *Effect:* Scans changed files for obvious errors (lint, types) before commit.
 
 ## 7. Dependencies & Capabilities
 
 ### Agents
--   **Reviewer**: `@[.opencode/agents/reviewer.md]` - General code quality.
--   **Security**: `@[.opencode/agents/security.md]` - Vulnerability scanning.
+
+- **Reviewer**: `@[.opencode/agents/reviewer.md]` - General code quality.
+- **Security**: `@[.opencode/agents/security.md]` - Vulnerability scanning.
 
 ### Skills
--   **Security Audit**: `@[.opencode/skills/security-audit/SKILL.md]` - Automated checking.
+
+- **Security Audit**: `@[.opencode/skills/security-audit/SKILL.md]` - Automated checking.
 
 ## 8. Boundaries
 
 **Will:**
--   Point out specific lines of code.
--   Suggest concrete fixes.
--   Block "unsafe" code.
+
+- Point out specific lines of code.
+- Suggest concrete fixes.
+- Block "unsafe" code.
 
 **Will Not:**
--   **Fix the code**: It only comments. Use `/soc-improve` to fix.
--   **Judge Aesthetics**: Unless it violates "Intentional Minimalism."
+
+- **Fix the code**: It only comments. Use `/soc-improve` to fix.
+- **Judge Aesthetics**: Unless it violates "Intentional Minimalism."
+
+## User Instruction
+
+The user have executed the `/soc-review` command by parsing the user's arguments provided in `<user-instruction>$ARGUMENTS</user-instruction>`, then route to the appropriate reviewer agent based on the specified scope and security flag, load the target code and associated context (such as implementation_plan.md), perform static analysis to identify code smells, trace variable data flow for logic verification, check for security vulnerabilities when `--security` is specified, categorize findings by severity (Critical, Warning, Info), provide specific line-by-line feedback with concrete fix suggestions, generate a comprehensive review report with verdict and summary, and block merges if critical issues are detected.

package/.opencode/commands/soc-test.md

@@ -5,9 +5,11 @@ description: Test generation and execution
 # /soc-test
 
 ## 1. Command Overview
+
 The `/soc-test` command is the "Quality Gatekeeper." It generates, runs, and reports on tests. It ensures that no code is shipped without verification. It triggers the `quality` agent to write unit, integration, or E2E tests and uses the `reviewer` agent to analyze coverage.
 
 ## 2. Triggers & Routing
+
 The command determines the scope and tool based on the arguments.
 
 | Trigger Scenario | Flag | Target Agent | Tool Used |
@@ -18,39 +20,46 @@ The command determines the scope and tool based on the arguments.
 | **Coverage Check**| `--coverage` | `[reviewer]` | Istanbul/C8 |
 
 ## 3. Usage & Arguments
+
 ```bash
 /soc-test [target] [flags]
 ```
 
 ### Arguments
--   **`[target]`**: File or directory to test (e.g., `src/utils/math.ts`).
+
+- **`[target]`**: File or directory to test (e.g., `src/utils/math.ts`).
 
 ### Flags
--   **`--type [unit|integration|e2e]`**: (Optional) Default: `unit`.
--   **`--coverage`**: Generates a coverage report.
--   **`--watch`**: Runs in watch mode (interactive).
+
+- **`--type [unit|integration|e2e]`**: (Optional) Default: `unit`.
+- **`--coverage`**: Generates a coverage report.
+- **`--watch`**: Runs in watch mode (interactive).
 
 ## 4. Behavioral Flow (Orchestration)
 
 ### Phase 1: Context & Gap Analysis
-1.  **Read**: Analyzes the source code in `[target]`.
-2.  **Scan**: Checks for existing `.test.ts` or `_test.py` files.
-3.  **Plan**: Identifies missing test cases (Edge cases, Error states, Happy path).
+
+1. **Read**: Analyzes the source code in `[target]`.
+2. **Scan**: Checks for existing `.test.ts` or `_test.py` files.
+3. **Plan**: Identifies missing test cases (Edge cases, Error states, Happy path).
 
 ### Phase 2: Generation (The Writer)
+
 The command prompts the `quality` agent:
 > "Generate **[Type]** tests for **[Target]**.
 > Ensure **[Coverage]**.
 > Mock dependencies: **[External Services]**."
 
 ### Phase 3: Execution (The Runner)
-1.  **Run**: Executes the test command (e.g., `npm test`).
-2.  **Report**: Captures `stdout/stderr`.
-3.  **Reflect**: If tests fail, it suggests fixes (or fixes them if in `implement` mode).
+
+1. **Run**: Executes the test command (e.g., `npm test`).
+2. **Report**: Captures `stdout/stderr`.
+3. **Reflect**: If tests fail, it suggests fixes (or fixes them if in `implement` mode).
 
 ## 5. Output Guidelines (The Contract)
 
 ### Test Execution Report
+
 ```markdown
 ## Test Report: [Target]
 
@@ -72,38 +81,51 @@ The command prompts the `quality` agent:
 ## 6. Examples
 
 ### A. Unit Test Generation
+
 ```bash
 /soc-test src/utils/currency.ts --type unit
 ```
+
 *Effect:* Generates `src/utils/currency.test.ts` covering rounding logic and currency codes.
 
 ### B. Integration Test
+
 ```bash
 /soc-test src/api/auth --type integration
 ```
+
 *Effect:* Sets up a mock database and tests the `/login` flow including DB persistence.
 
 ## 7. Dependencies & Capabilities
 
 ### Agents
--   **Quality Assurance**: `@[.opencode/agents/quality.md]` - Primary agent for test generation.
--   **Reviewer**: `@[.opencode/agents/reviewer.md]` - For evaluating test coverage and effectiveness.
+
+- **Quality Assurance**: `@[.opencode/agents/quality.md]` - Primary agent for test generation.
+- **Reviewer**: `@[.opencode/agents/reviewer.md]` - For evaluating test coverage and effectiveness.
 
 ### Skills
--   **Self Check**: `@[.opencode/skills/self-check/SKILL.md]` - Verifying test results against requirements.
--   **Debug Protocol**: `@[.opencode/skills/debug-protocol/SKILL.md]` - Analyzing test failures.
+
+- **Self Check**: `@[.opencode/skills/self-check/SKILL.md]` - Verifying test results against requirements.
+- **Debug Protocol**: `@[.opencode/skills/debug-protocol/SKILL.md]` - Analyzing test failures.
 
 ### MCP Integration
--   **`run_command`**: Executing test runners (Jest, Vitest, Pytest).
--   **`filesystem`**: processing integration test artifacts or coverage reports.
+
+- **`run_command`**: Executing test runners (Jest, Vitest, Pytest).
+- **`filesystem`**: processing integration test artifacts or coverage reports.
 
 ## 8. Boundaries
 
 **Will:**
--   Generate standard test files using the project's framework.
--   Run tests and parse output.
--   Mock external dependencies (S3, Stripe) to prevent flake.
+
+- Generate standard test files using the project's framework.
+- Run tests and parse output.
+- Mock external dependencies (S3, Stripe) to prevent flake.
 
 **Will Not:**
--   **Guarantee 100% Logic Coverage**: It covers code paths, not necessarily business intent.
--   **Debug Production**: Tests run in `test` environment only.
+
+- **Guarantee 100% Logic Coverage**: It covers code paths, not necessarily business intent.
+- **Debug Production**: Tests run in `test` environment only.
+
+## User Instruction
+
+The user have executed the `/soc-test` command by parsing the user's arguments provided in `<user-instruction>$ARGUMENTS</user-instruction>`, then route to the quality agent to generate and run tests for the specified target, analyze the source code to understand what needs testing and check for existing test files, determine the test type (unit, integration, or e2e) based on flags or code context, generate comprehensive test cases covering happy paths, edge cases, and error states, mock external dependencies to prevent test flakiness, execute the test runner and capture output, analyze any test failures using the debug protocol skill, generate a coverage report when `--coverage` is specified, and provide a comprehensive test execution report showing status, failures with diagnosis, and coverage metrics.