opencode-multiagent 0.2.1 → 0.4.0

package/skills/cek-context-engineering/manifest.json

@@ -9,9 +9,7 @@
     "lost in middle",
     "context design"
   ],
-  "applicable_agents": [
-    "critic"
-  ],
+  "applicable_agents": ["planner"],
   "max_context_tokens": 2600,
   "entry_file": "SKILL.md"
 }

package/skills/cek-prompt-engineering/SKILL.md

@@ -37,6 +37,7 @@ Request step-by-step reasoning before the final answer. Add "Let's think step by
 Analyze this bug report and determine root cause.
 
 Think step by step:
+
 1. What is the expected behavior?
 2. What is the actual behavior?
 3. What changed recently that could cause this?
@@ -100,6 +101,7 @@ Set global behavior and constraints that persist across the conversation. Define
 System: You are a senior backend engineer specializing in API design.
 
 Rules:
+
 - Always consider scalability and performance
 - Suggest RESTful patterns by default
 - Flag security concerns immediately
@@ -107,6 +109,7 @@ Rules:
 - Use early return pattern
 
 Format responses as:
+
 1. Analysis
 2. Recommendation
 3. Code example
@@ -249,7 +252,7 @@ Only add context Claude doesn't already have. Challenge each piece of informatio
 
 **Good example: Concise** (approximately 50 tokens):
 
-````markdown  theme={null}
+````markdown theme={null}
 ## Extract PDF text
 
 Use pdfplumber for text extraction:
@@ -264,7 +267,7 @@ with pdfplumber.open("file.pdf") as pdf:
 
 **Bad example: Too verbose** (approximately 150 tokens):
 
-```markdown  theme={null}
+```markdown theme={null}
 ## Extract PDF text
 
 PDF (Portable Document Format) files are a common file format that contains
@@ -290,7 +293,7 @@ Use when:
 
 Example:
 
-```markdown  theme={null}
+```markdown theme={null}
 ## Code review process
 
 1. Analyze the code structure and organization
@@ -309,7 +312,7 @@ Use when:
 
 Example:
 
-````markdown  theme={null}
+````markdown theme={null}
 ## Generate report
 
 Use this template and customize as needed:
@@ -332,7 +335,7 @@ Use when:
 
 Example:
 
-````markdown  theme={null}
+````markdown theme={null}
 ## Database migration
 
 Run exactly this script:
@@ -504,12 +507,12 @@ LLMs respond to the same persuasion principles as humans. Understanding this psy
 
 ## Principle Combinations by Prompt Type
 
-| Prompt Type | Use | Avoid |
-|------------|-----|-------|
+| Prompt Type          | Use                                   | Avoid               |
+| -------------------- | ------------------------------------- | ------------------- |
 | Discipline-enforcing | Authority + Commitment + Social Proof | Liking, Reciprocity |
-| Guidance/technique | Moderate Authority + Unity | Heavy authority |
-| Collaborative | Unity + Commitment | Authority, Liking |
-| Reference | Clarity only | All persuasion |
+| Guidance/technique   | Moderate Authority + Unity            | Heavy authority     |
+| Collaborative        | Unity + Commitment                    | Authority, Liking   |
+| Reference            | Clarity only                          | All persuasion      |
 
 ## Why This Works: The Psychology
 

package/skills/cek-prompt-engineering/manifest.json

@@ -9,9 +9,7 @@
     "rewrite prompt",
     "instruction design"
   ],
-  "applicable_agents": [
-    "critic"
-  ],
+  "applicable_agents": ["planner"],
   "max_context_tokens": 2200,
   "entry_file": "SKILL.md"
 }

package/skills/cek-test-prompt/SKILL.md

@@ -16,10 +16,9 @@ Run scenarios without the prompt (RED - watch agent behavior), write prompt addr
 **Core principle:** If you didn't watch an agent fail without the prompt, you don't know what the prompt needs to fix.
 
 **REQUIRED BACKGROUND:**
-- You MUST understand `tdd:test-driven-development` - defines RED-GREEN-REFACTOR cycle
-- You SHOULD understand `prompt-engineering` skill - provides prompt optimization techniques
 
-**Related skill:** See `test-skill` for testing discipline-enforcing skills specifically. This command covers ALL prompts.
+- You MUST understand TDD methodology (RED-GREEN-REFACTOR cycle)
+- You SHOULD understand `cek-prompt-engineering` skill - provides prompt optimization techniques
 
 ## When to Use
 
@@ -40,26 +39,26 @@ Test before deployment when:
 
 ## Prompt Types & Testing Strategies
 
-| Prompt Type | Test Focus | Example |
-|-------------|------------|---------|
-| **Instruction** | Does agent follow steps correctly? | Command that performs git workflow |
-| **Discipline-enforcing** | Does agent resist rationalization under pressure? | Skill requiring TDD compliance |
-| **Guidance** | Does agent apply advice appropriately? | Skill with architecture patterns |
-| **Reference** | Is information accurate and accessible? | API documentation skill |
-| **Subagent** | Does subagent accomplish task reliably? | Task tool prompt for code review |
+| Prompt Type              | Test Focus                                        | Example                            |
+| ------------------------ | ------------------------------------------------- | ---------------------------------- |
+| **Instruction**          | Does agent follow steps correctly?                | Command that performs git workflow |
+| **Discipline-enforcing** | Does agent resist rationalization under pressure? | Skill requiring TDD compliance     |
+| **Guidance**             | Does agent apply advice appropriately?            | Skill with architecture patterns   |
+| **Reference**            | Is information accurate and accessible?           | API documentation skill            |
+| **Subagent**             | Does subagent accomplish task reliably?           | Task tool prompt for code review   |
 
 Different types need different test scenarios (covered in sections below).
 
 ## TDD Mapping for Prompt Testing
 
-| TDD Phase | Prompt Testing | What You Do |
-|-----------|----------------|-------------|
-| **RED** | Baseline test | Run scenario WITHOUT prompt using subagent, observe behavior |
-| **Verify RED** | Document behavior | Capture exact agent actions/reasoning verbatim |
-| **GREEN** | Write prompt | Address specific baseline failures |
-| **Verify GREEN** | Test with prompt | Run WITH prompt using subagent, verify improvement |
-| **REFACTOR** | Optimize prompt | Improve clarity, close loopholes, reduce tokens |
-| **Stay GREEN** | Re-verify | Test again with fresh subagent, ensure still works |
+| TDD Phase        | Prompt Testing    | What You Do                                                  |
+| ---------------- | ----------------- | ------------------------------------------------------------ |
+| **RED**          | Baseline test     | Run scenario WITHOUT prompt using subagent, observe behavior |
+| **Verify RED**   | Document behavior | Capture exact agent actions/reasoning verbatim               |
+| **GREEN**        | Write prompt      | Address specific baseline failures                           |
+| **Verify GREEN** | Test with prompt  | Run WITH prompt using subagent, verify improvement           |
+| **REFACTOR**     | Optimize prompt   | Improve clarity, close loopholes, reduce tokens              |
+| **Stay GREEN**   | Re-verify         | Test again with fresh subagent, ensure still works           |
 
 ## Why Use Subagents for Testing?
 
@@ -111,6 +110,7 @@ Make an appropriate commit.
 ```
 
 **Baseline behavior (without prompt):**
+
 - Agent might commit all files (including experimental)
 - Might skip running tests first
 - Might write vague commit message
@@ -140,6 +140,7 @@ Choose A, B, or C. Be honest.
 ```
 
 **Baseline behavior (without skill):**
+
 - Agent chooses B or C
 - Rationalizations: "manually tested", "tests after achieve same goals", "deleting wasteful"
 
@@ -160,6 +161,7 @@ Propose an architecture.
 ```
 
 **Baseline behavior (without skill):**
+
 - Agent might propose synchronous processing (too slow)
 - Might miss retry/fallback mechanisms
 - Might not consider event ordering
@@ -179,6 +181,7 @@ What's the retry strategy for failed requests?
 ```
 
 **Baseline behavior (without reference):**
+
 - Agent guesses or provides generic advice
 - Misses product-specific details
 - Provides outdated information
@@ -241,16 +244,18 @@ Clear steps addressing baseline failures:
 Add explicit counters for each rationalization:
 
 ## The Iron Law
+
 Write code before test? Delete it. Start over.
 
 **No exceptions:**
+
 - Don't keep as "reference"
 - Don't "adapt" while writing tests
 - Delete means delete
 
-| Excuse | Reality |
-|--------|---------|
-| "Already manually tested" | Ad-hoc ≠ systematic. No record, can't re-run. |
+| Excuse                     | Reality                                           |
+| -------------------------- | ------------------------------------------------- |
+| "Already manually tested"  | Ad-hoc ≠ systematic. No record, can't re-run.     |
 | "Tests after achieve same" | Tests-after = verifying. Tests-first = designing. |
 ```
 
@@ -264,6 +269,7 @@ Pattern with clear applicability:
 **When to use:** >1000 events/sec, async operations, resilience required
 
 **Pattern:**
+
 1. Queue-based ingestion (decouple receipt from processing)
 2. Worker pools (parallel processing)
 3. Dead letter queue (failed events)
@@ -309,6 +315,7 @@ description: "Green test for [prompt-name]"
 ```
 
 **Success criteria:**
+
 - Agent follows prompt instructions
 - Baseline failures no longer occur
 - Agent cites prompt when relevant
@@ -418,6 +425,7 @@ to submit. If validation fails, show errors to the user.
 **Re-test same scenarios with updated prompt using fresh subagents.**
 
 Agent should:
+
 - Still follow instructions correctly
 - Show improved understanding
 - Reference updated sections when relevant
@@ -470,6 +478,7 @@ For critical prompts, test under extreme conditions.
 
 ```markdown
 Launch subagent with:
+
 - Maximum pressure scenarios
 - Ambiguous edge cases
 - Contradictory constraints
@@ -546,6 +555,7 @@ Testing command: `/git:commit` - should create conventional commits with verific
 Task: You need to commit changes.
 
 Modified files:
+
 - src/payment.ts (new feature complete)
 - src/experimental.ts (work in progress, broken)
 - tests/payment.test.ts (tests for new feature)
@@ -677,13 +687,13 @@ Kept: Critical rules and process steps
 
 ## Quick Reference
 
-| Prompt Type | RED Test | GREEN Fix | REFACTOR Focus |
-|-------------|----------|-----------|----------------|
-| **Instruction** | Does agent skip steps? | Add explicit steps/verification | Reduce tokens, improve clarity |
-| **Discipline** | Does agent rationalize? | Add counters for rationalizations | Close new loopholes |
-| **Guidance** | Does agent misapply? | Clarify when/how to use | Add examples, simplify |
-| **Reference** | Is information missing/wrong? | Add accurate details | Organize for findability |
-| **Subagent** | Does task fail? | Clarify task/constraints | Optimize for token cost |
+| Prompt Type     | RED Test                      | GREEN Fix                         | REFACTOR Focus                 |
+| --------------- | ----------------------------- | --------------------------------- | ------------------------------ |
+| **Instruction** | Does agent skip steps?        | Add explicit steps/verification   | Reduce tokens, improve clarity |
+| **Discipline**  | Does agent rationalize?       | Add counters for rationalizations | Close new loopholes            |
+| **Guidance**    | Does agent misapply?          | Clarify when/how to use           | Add examples, simplify         |
+| **Reference**   | Is information missing/wrong? | Add accurate details              | Organize for findability       |
+| **Subagent**    | Does task fail?               | Clarify task/constraints          | Optimize for token cost        |
 
 ## Integration with Prompt Engineering
 

package/skills/cek-test-prompt/manifest.json

@@ -9,9 +9,7 @@
     "prompt behavior",
     "red green prompt"
   ],
-  "applicable_agents": [
-    "critic"
-  ],
+  "applicable_agents": ["planner"],
   "max_context_tokens": 2400,
   "entry_file": "SKILL.md"
 }