super-opencode 1.1.0 → 1.1.2

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

@@ -1,99 +1,99 @@
----
-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 |
-| :--- | :--- | :--- | :--- |
-| **New Project** | `plan` | `[pm-agent]` | Create `task.md` |
-| **Progress Check** | `status` | `[pm-agent]` | Read/Update `task.md` |
-| **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.
-
-### Flags
--   **`--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 `[ ]`.
-
-### Phase 2: Do (Tracking)
--   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.
-
-## 5. Output Guidelines (The Contract)
-
-### Project Status Report
-```markdown
-## Project Status: [Phase]
-
-### Progress
--   **Completed**: 3/5 Tasks (60%)
--   **Current Focus**: Implementing API Auth
-
-### Task List
--   [x] Setup DB Schema
--   [/] **Implement Login Route** (Active)
--   [ ] Write Tests
-
-### Blockers
--   Waiting for API Key from user.
-```
-
-## 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.
-
-### Skills
--   **Reflexion**: `@[.opencode/skills/reflexion/SKILL.md]` - For unblocking the team.
-
-### MCP Integration
--   **`filesystem`**: Managing `task.md` and `implementation_plan.md`.
-
-## 8. Boundaries
-
-**Will:**
--   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.
+---
+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 |
+| :--- | :--- | :--- | :--- |
+| **New Project** | `plan` | `[pm-agent]` | Create `task.md` |
+| **Progress Check** | `status` | `[pm-agent]` | Read/Update `task.md` |
+| **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.
+
+### Flags
+-   **`--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 `[ ]`.
+
+### Phase 2: Do (Tracking)
+-   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.
+
+## 5. Output Guidelines (The Contract)
+
+### Project Status Report
+```markdown
+## Project Status: [Phase]
+
+### Progress
+-   **Completed**: 3/5 Tasks (60%)
+-   **Current Focus**: Implementing API Auth
+
+### Task List
+-   [x] Setup DB Schema
+-   [/] **Implement Login Route** (Active)
+-   [ ] Write Tests
+
+### Blockers
+-   Waiting for API Key from user.
+```
+
+## 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.
+
+### Skills
+-   **Reflexion**: `@[.opencode/skills/reflexion/SKILL.md]` - For unblocking the team.
+
+### MCP Integration
+-   **`filesystem`**: Managing `task.md` and `implementation_plan.md`.
+
+## 8. Boundaries
+
+**Will:**
+-   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.

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

@@ -1,105 +1,105 @@
----
-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 |
-| :--- | :--- | :--- | :--- |
-| **Quick Fact** | `--depth quick` | `[researcher]` | DuckDuckGo/Tavily |
-| **Docs Lookup** | `[topic]` | `[researcher]` | `context7` |
-| **Deep Dive** | `--depth deep` | `[researcher]` | Recursive Search |
-
-## 3. Usage & Arguments
-```bash
-/soc-research [topic] [flags]
-```
-
-### Arguments
--   **`[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`).
-
-## 4. Behavioral Flow (Orchestration)
-
-### Phase 1: Parsing
-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.
-
-### Phase 3: Reporting
--   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]
-
-### Executive Summary
-[Direct Answer]
-
-### Key Findings
-1.  **[Fact 1]**: [Detail]
-    *   *Source*: [Link]
-2.  **[Fact 2]**: [Detail]
-
-### Code Patterns (if applicable)
-```typescript
-// Verified pattern from docs
-const x = new Library();
-```
-
-### Conflicting Info
--   StackOverflow suggests X, but Official Docs say Y (Deprecated).
-```
-
-## 6. Examples
-
-### A. Library Selection
-```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.
-
-### Skills
--   **Sequential Thinking**: `@[.opencode/skills/sequential-thinking/SKILL.md]` - For resolving conflicts.
-
-### MCP Integration
--   **`tavily`**: Real-time web search.
--   **`context7`**: Documentation retrieval.
-
-## 8. Boundaries
-
-**Will:**
--   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.
+---
+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 |
+| :--- | :--- | :--- | :--- |
+| **Quick Fact** | `--depth quick` | `[researcher]` | DuckDuckGo/Tavily |
+| **Docs Lookup** | `[topic]` | `[researcher]` | `context7` |
+| **Deep Dive** | `--depth deep` | `[researcher]` | Recursive Search |
+
+## 3. Usage & Arguments
+```bash
+/soc-research [topic] [flags]
+```
+
+### Arguments
+-   **`[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`).
+
+## 4. Behavioral Flow (Orchestration)
+
+### Phase 1: Parsing
+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.
+
+### Phase 3: Reporting
+-   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]
+
+### Executive Summary
+[Direct Answer]
+
+### Key Findings
+1.  **[Fact 1]**: [Detail]
+    *   *Source*: [Link]
+2.  **[Fact 2]**: [Detail]
+
+### Code Patterns (if applicable)
+```typescript
+// Verified pattern from docs
+const x = new Library();
+```
+
+### Conflicting Info
+-   StackOverflow suggests X, but Official Docs say Y (Deprecated).
+```
+
+## 6. Examples
+
+### A. Library Selection
+```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.
+
+### Skills
+-   **Sequential Thinking**: `@[.opencode/skills/sequential-thinking/SKILL.md]` - For resolving conflicts.
+
+### MCP Integration
+-   **`tavily`**: Real-time web search.
+-   **`context7`**: Documentation retrieval.
+
+## 8. Boundaries
+
+**Will:**
+-   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.

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

@@ -1,102 +1,102 @@
----
-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 |
-| :--- | :--- | :--- | :--- |
-| **Logic/Bugs** | `--scope full` | `[reviewer]` | Correctness |
-| **Security** | `--security` | `[security]` | Injection, AuthZ |
-| **Style/Lint** | `--quick` | `[reviewer]` | Formatting, Naming |
-
-## 3. Usage & Arguments
-```bash
-/soc-review [target] [flags]
-```
-
-### Arguments
--   **`[target]`**: File, directory, or Pull Request ID to review.
-
-### Flags
--   **`--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).
-
-### 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)?
-
-### Phase 3: Reporting
--   Categorize findings by Severity (Critical, Warning, Info).
--   Reject if Critical issues exist.
-
-## 5. Output Guidelines (The Contract)
-
-### Code Review
-```markdown
-## Review: [Target]
-
-### Verdict
-❌ **Changes Requested** (1 Critical Issue)
-
-### Findings
-
-#### 🔴 Critical: SQL Injection
--   **File**: `src/api/search.ts:15`
--   **Code**: `db.query("SELECT * FROM users WHERE name = " + req.query.name)`
--   **Fix**: Use parameterized query `$1`.
-
-#### 🟡 Warning: Performance
--   **File**: `src/utils.ts:40`
--   **Issue**: `README.md` parsing is synchronous. Use `fs.promises`.
-
-### Summary
-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.
-
-### Skills
--   **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.
-
-**Will Not:**
--   **Fix the code**: It only comments. Use `/soc-improve` to fix.
--   **Judge Aesthetics**: Unless it violates "Intentional Minimalism."
+---
+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 |
+| :--- | :--- | :--- | :--- |
+| **Logic/Bugs** | `--scope full` | `[reviewer]` | Correctness |
+| **Security** | `--security` | `[security]` | Injection, AuthZ |
+| **Style/Lint** | `--quick` | `[reviewer]` | Formatting, Naming |
+
+## 3. Usage & Arguments
+```bash
+/soc-review [target] [flags]
+```
+
+### Arguments
+-   **`[target]`**: File, directory, or Pull Request ID to review.
+
+### Flags
+-   **`--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).
+
+### 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)?
+
+### Phase 3: Reporting
+-   Categorize findings by Severity (Critical, Warning, Info).
+-   Reject if Critical issues exist.
+
+## 5. Output Guidelines (The Contract)
+
+### Code Review
+```markdown
+## Review: [Target]
+
+### Verdict
+❌ **Changes Requested** (1 Critical Issue)
+
+### Findings
+
+#### 🔴 Critical: SQL Injection
+-   **File**: `src/api/search.ts:15`
+-   **Code**: `db.query("SELECT * FROM users WHERE name = " + req.query.name)`
+-   **Fix**: Use parameterized query `$1`.
+
+#### 🟡 Warning: Performance
+-   **File**: `src/utils.ts:40`
+-   **Issue**: `README.md` parsing is synchronous. Use `fs.promises`.
+
+### Summary
+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.
+
+### Skills
+-   **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.
+
+**Will Not:**
+-   **Fix the code**: It only comments. Use `/soc-improve` to fix.
+-   **Judge Aesthetics**: Unless it violates "Intentional Minimalism."