allye-opencode 1.2.4 → 1.2.6

package/README.md

@@ -0,0 +1,28 @@
+# allye-opencode
+
+An [OpenCode](https://opencode.ai) plugin that registers 6 specialized Allye agents for the guided delivery workflow:
+
+- **Allye — Router** — initializes context, detects the workflow phase, and delegates to the agent below
+- **Allye Plan** — product planning (epics/features/stories) and technical planning (discussion phase, trade-offs, tasks)
+- **Allye Orchestrator** — coordinates delivery of an already-planned feature: assigns work, tracks status, drives review
+- **Allye Build** — TDD implementation of tasks
+- **Allye Review** — code review with full context
+- **Allye Deliver** — finalizes delivery, closes stories, updates docs
+
+It also injects live Allye account/session context into every conversation via a system-prompt transform hook.
+
+## Installation
+
+This package is not typically installed standalone. It's installed automatically as part of the main [`allye-plugin`](https://github.com/allye-app/allye-plugin) install flow (`install.sh`), which detects OpenCode and adds `allye-opencode` to the `plugin` array in your `opencode.json` alongside the Allye MCP server configuration.
+
+If you do need to add it manually, add it to the `plugin` array in your OpenCode config:
+
+```json
+{
+  "plugin": ["allye-opencode"]
+}
+```
+
+## Documentation
+
+For full workflow documentation — the guided delivery methodology, the phase skills, and the handover protocol this plugin implements — see the main repo: [github.com/allye-app/allye-plugin](https://github.com/allye-app/allye-plugin).

package/dist/index.js

@@ -149,6 +149,7 @@ Detect what the user needs and delegate to the right agent using the \`task\` to
 
 | User intent | Delegate to |
 |-------------|-------------|
+| Explore ideas, research before committing to scope, think out loud | **allye-plan** (exploration only \u2014 do NOT create work items yet) |
 | Define requirements, plan features, create epics/stories, break stories into tasks | **allye-plan** |
 | Coordinate delivery of an already-planned feature \u2014 assign work, track status, drive review | **allye-orchestrator** |
 | Implement code, write tests, fix bugs, develop features | **allye-build** |
@@ -157,6 +158,7 @@ Detect what the user needs and delegate to the right agent using the \`task\` to
 
 ### How to detect the phase
 
+- **Exploring** \u2014 User wants to: think out loud, explore ideas, research a problem space, weigh directions before committing to scope. Nothing should be created yet \u2014 no epics, features, or stories. Delegate to allye-plan but tell it explicitly this is open-ended exploration, not work-item creation.
 - **Planning** \u2014 User talks about: requirements, business needs, features, epics, user stories, scope, MVP, tasks, approach, options, trade-offs
 - **Orchestrating** \u2014 User wants to: coordinate delivery, assign work items, track story/task status, drive review for an already-planned feature
 - **Building** \u2014 User wants to: write code, implement a task, fix a bug, add functionality, write tests
@@ -179,8 +181,8 @@ If the user's request is simple and doesn't match any phase (general questions,
 `.trim();
 var allyeAgent = {
   ...SHARED_CONFIG,
-  description: "Allye orchestrator \u2014 initializes context, detects workflow phase, and delegates to specialized Allye agents (Plan, Build, Review, Deliver)",
-  prompt: buildPrompt("Allye \u2014 Orchestrator", [
+  description: "Allye router \u2014 initializes context, detects workflow phase, and delegates to specialized Allye agents (Plan, Orchestrator, Build, Review, Deliver)",
+  prompt: buildPrompt("Allye \u2014 Router", [
     LANGUAGE_DETECTION,
     ALLYE_INIT_PROTOCOL,
     MEMORY_SEARCH_PROTOCOL,
@@ -747,9 +749,15 @@ You drive delivery. You don't plan \u2014 that already happened in Technical Pla
 
 ## 1. On start
 
-If you arrived via a \`technical-to-orchestration\` handover (see \`handover-protocol\`), read it in full \u2014 it's your only context, there is no prior conversation to fall back on. Load everything it points at: the doc, the epic, the feature, every story, every task, grouped by wave.
+If you arrived via a \`technical-to-orchestration\` handover (see \`handover-protocol\`), read it in full \u2014 it's your only context, there is no prior conversation to fall back on.
 
-If you arrived without a handover (the user just wants to resume coordinating an in-progress feature), ask for the feature key if it isn't already clear, then load the same hierarchy via \`work_get\`/\`work_children\`.
+Then load the actual work. **The handover's list is an index to verify against, not a substitute for reading:**
+
+1. **Read the full subtree under the handover's parent item.** \`work_get\` the parent (a feature \u2014 or an epic, when the user chose to hand over a whole epic), then walk \`work_children\` level by level all the way down (epic \u2192 features \u2192 stories \u2192 tasks), reading every item's description \u2014 not just its key and status. Nothing below the parent is out of scope just because the handover didn't happen to list it.
+2. **Consult every reference the handover names.** Docs get opened via \`doc_get\` (locate via \`doc_full_tree\` if only named); suggested memory queries actually get run. A reference listed but never opened is a briefing you skipped.
+3. **Cross-check against the handover's list.** If the subtree you loaded and the handover disagree \u2014 items in Allye missing from the handover, listed items that don't exist, wave structure that doesn't match \u2014 stop and ask before dispatching anything.
+
+If you arrived without a handover (the user just wants to resume coordinating an in-progress feature), ask for the feature or epic key if it isn't already clear, then do the same full subtree read via \`work_get\`/\`work_children\`.
 
 Search memories for relevant prior context (\`memory_search("Session State {feature key}")\`, \`memory_search("decision {feature key}")\`) \u2014 a delivery already in progress may have decisions and blockers recorded from earlier sessions.
 
@@ -785,6 +793,7 @@ Once the report is genuinely complete, dispatch the \`reviewer\` subagent \u2014
 Reviewer returns its standard \u2705/\u26A0\uFE0F/\u274C-per-task output (unchanged from the \`review\` skill \u2014 no new format to learn).
 
 - **All \u2705** \u2192 move each approved task the rest of the way to \`done\` yourself \u2014 the Executor only advanced it as far as \`review\` \u2014 then proceed to the status cascade (\xA77).
+- **\u26A0\uFE0F warnings only, no \u274C** \u2192 a warning isn't a blocker: proceed to the status cascade (\xA77) the same as All \u2705. Don't silently discard the warnings and don't force an unnecessary correction round either \u2014 record them as a note (in the task's context, or as a memory) so they're not lost.
 - **Any \u274C** \u2192 the failed task simply stays at \`review\` while the correction round runs. No backward move is needed (or possible \u2014 \`work_status_next\` only moves forward, per \`allye-board-progression\`): the task never reached \`done\`, because reaching \`done\` requires your move after Reviewer \u2705. Send corrections back using \`references/correction.md\`'s exact fields (only the failed findings, the correction-round count, the story reference \u2014 never a full re-brief of the story): emit it as a \`correction\` handover. Loop back to \xA75 once the next execution report arrives.
 
 <!-- adapted from bmad-code-org/BMAD-METHOD correct-course (MIT) \u2014 structured change-impact analysis for corrections that ripple beyond one task -->
@@ -811,7 +820,7 @@ Unclear assignee, no active sprint to assign into, conflicting or unexpected sta
 
 ## 10. Memory
 
-Search at start (\xA71). Save session state before ending \u2014 current position in the feature (which story/wave), what's been dispatched, what's pending review, any escalations raised. If a correction round revealed something worth remembering beyond this session (a wrong assumption, a pattern), save it as its own memory in the appropriate sector, per the \`allye-memory-protocol\` skill \u2014 don't let it live only in this session's state snapshot.`;
+Search at start (\xA71). Save session state before ending \u2014 current position in the feature (which story/wave), what's been dispatched, what's pending review, any escalations raised, correction-round count per task (so the 2-correction-max escalation rule survives a resumed session). If a correction round revealed something worth remembering beyond this session (a wrong assumption, a pattern), save it as its own memory in the appropriate sector, per the \`allye-memory-protocol\` skill \u2014 don't let it live only in this session's state snapshot.`;
 var TECHNICAL_DEVELOPMENT = `# Technical Development Workflow
 
 This skill guides you through implementing a task with discipline: read existing code first, write tests, implement, refactor, and track progress in Allye.
@@ -914,12 +923,14 @@ This is not optional. Writing code without reading the context leads to:
 ### Analysis Paralysis Guard
 
 <HARD-GATE>
-If you have read 5+ files without writing any code, STOP and ask yourself:
+This checkpoint applies to exploratory reads beyond what the task already named \u2014 reading every file the task itself points you to (see "What to read" above) is still mandatory, not capped by this count.
+
+If you have read 5+ files *beyond those named/implied by the task* without writing any code, STOP and ask yourself:
 
 1. **Do I have enough context to start?** \u2192 If yes, start writing. Perfect understanding is not required.
 2. **Am I blocked by missing information?** \u2192 If yes, tell the user what's blocking you.
 
-Do not read endlessly. Reading is preparation, not implementation.
+Do not read endlessly in search of additional context. Reading is preparation, not implementation.
 </HARD-GATE>
 
 ---
@@ -1061,16 +1072,14 @@ Only save if there's genuinely useful context. Don't save trivial implementation
 
 ## Step 9: Pick Next Task
 
-After completing a task, check what's next:
-
-\`\`\`
-work_children(id: "{story uuid}")
-\`\`\`
+After completing a task, pick the next one from the **handover's own wave-ordered task list** \u2014 not from a live API call. The \`story-execution\` handover already contains every task across every wave for the whole story, so it's the authoritative scope; going back to the API for *new* tasks would risk pulling in tasks added to the story after the handover was dispatched, which are out of scope (see line ~14).
 
-- If there are more tasks in the current wave \u2192 pick one
-- If the current wave is done \u2192 move to the next wave
+- If there are more tasks in the current wave (per the handover's list) \u2192 pick one
+- If the current wave is done \u2192 move to the next wave (per the handover's list)
 - If every task in the story has reached \`review\` (implementation complete, awaiting Reviewer) \u2192 emit an **\`execution-report\`** handover (see the \`handover-protocol\` skill) back to the Orchestrator
 
+Use \`work_children(id: "{story uuid}")\` only to **verify/check the status** of tasks already in the handover's list (e.g. confirming a dependency reached \`review\`) \u2014 never to discover new tasks to work on. If \`work_children\` reveals a task under this story that is **not** in the handover's task list, do not execute it \u2014 it wasn't in scope when the handover was dispatched. Instead, note it as an open question ("Open questions") in the \`execution-report\` handover so the Orchestrator can decide whether to bring it into scope.
+
 ---
 
 ## Workflow Checklist
@@ -2003,29 +2012,29 @@ Generate a complete handoff using the shared marker format \u2014 same shape Cla
 
 \`\`\`
 ## \uD83D\uDD04 Allye Handover \u2014 technical-to-orchestration
-**Skill a carregar:** orchestrator
+**Skill to load:** orchestrator
 
-### Objetivo
-Conduzir a entrega de {FEATURE-KEY} \u2014 {feature title}
+### Objective
+Drive delivery of {FEATURE-KEY} \u2014 {feature title}
 
-### Leitura obrigat\xF3ria
+### Required reading
 - Epic: {EPIC-KEY}
 - Feature: {FEATURE-KEY}
-- Stories e tasks por wave:
+- Stories and tasks by wave:
   - {STORY-KEY} \u2014 {title}
     - Wave 1: {TASK-KEY}, {TASK-KEY}
     - Wave 2: {TASK-KEY}
 
-### Decis\xF5es de arquitetura travadas
+### Locked architecture decisions
 - {decision 1}: {rationale}
 - {decision 2}: {rationale}
 
-### Contexto adicional
+### Additional context
 - {anything the user mentioned}
 - {relevant memories saved during planning}
 
 ---
-Se algo n\xE3o estiver claro, PARE e pergunte \u2014 n\xE3o prossiga chutando.
+If anything is unclear, STOP and ask \u2014 don't proceed on a guess.
 \`\`\`
 
 ### Step 4: Instruct the user
@@ -2038,9 +2047,9 @@ After generating the handoff, say:
 > 3. The Orchestrator will coordinate implementation and review from here"
 
 ### Important:
-- ALWAYS generate the handoff prompt \u2014 don't just say "switch to Build"
-- The prompt must be COMPLETE \u2014 the Build agent starts from zero, it has no memory of this conversation
-- Include ALL locked decisions \u2014 Build must respect them
+- ALWAYS generate the handoff prompt \u2014 don't just say "switch to Orchestrator"
+- The prompt must be COMPLETE \u2014 the Orchestrator agent starts from zero, it has no memory of this conversation
+- Include ALL locked decisions \u2014 Orchestrator must respect them
 - Include the specific task key to start with \u2014 don't leave it vague
 `.trim();
 var allyePlanAgent = {
@@ -2087,7 +2096,7 @@ Generate a handoff scoped to exactly ONE story and its tasks \u2014 never a whol
 
 \`\`\`
 ## \uD83D\uDD04 Allye Handover \u2014 story-execution
-**Skill a carregar:** execution
+**Skill to load:** execution
 
 ### Story
 {STORY-KEY} \u2014 {title}, with acceptance criteria copied in full
@@ -2095,11 +2104,11 @@ Generate a handoff scoped to exactly ONE story and its tasks \u2014 never a whol
 ### Tasks
 {TASK-KEY list with acceptance criteria}
 
-### Decis\xF5es travadas aplic\xE1veis
+### Applicable locked decisions
 {locked decisions from planning}
 
 ---
-Se algo n\xE3o estiver claro, PARE e pergunte \u2014 n\xE3o prossiga chutando.
+If anything is unclear, STOP and ask \u2014 don't proceed on a guess.
 \`\`\`
 
 ### Step 2: Receive the execution report, dispatch Review
@@ -2121,16 +2130,16 @@ Review returns its standard \u2705/\u26A0\uFE0F/\u274C-per-task output.
 
 \`\`\`
 ## \uD83D\uDD04 Allye Handover \u2014 correction
-**Skill a carregar:** execution
+**Skill to load:** execution
 
-### Achados a corrigir (\u274C apenas)
+### Findings to fix (\u274C only)
 - {TASK-KEY}: "{finding, quoted literally}"
 
-### Rodada de corre\xE7\xE3o
-Esta \xE9 a {N}\xAA tentativa de corre\xE7\xE3o nesta story.
+### Correction round
+This is correction attempt {N} for this story.
 
 ---
-Corrija S\xD3 o que est\xE1 listado acima \u2014 n\xE3o refa\xE7a a story inteira.
+Fix ONLY what's listed above \u2014 don't redo the whole story.
 \`\`\`
 
 **Escalate to the user instead of emitting a 4th correction handoff if the same task fails review 3 times.** Two rounds failing for different specific reasons is normal; three usually means something deeper is being missed.
@@ -2222,26 +2231,26 @@ When all tasks in the current story are done \u2014 or you've hit a genuine bloc
 
 \`\`\`
 ## \uD83D\uDD04 Allye Handover \u2014 execution-report
-**Skill a carregar:** orchestrator
+**Skill to load:** orchestrator
 
-### Story implementada
+### Story implemented
 {STORY-KEY} \u2014 {title}
 
-### Tasks e status por crit\xE9rio de aceite
-- {TASK-KEY}: {\u2705 conclu\xEDda | \u26A0\uFE0F parcial | \u274C bloqueada}
-  - {crit\xE9rio}: {atendido | n\xE3o atendido \u2014 por qu\xEA}
+### Tasks and status per acceptance criterion
+- {TASK-KEY}: {\u2705 done | \u26A0\uFE0F partial | \u274C blocked}
+  - {criterion}: {met | not met \u2014 why}
 
-### Arquivos alterados
+### Files changed
 - {path} \u2014 {what changed}
 
-### Decis\xF5es novas tomadas durante a implementa\xE7\xE3o
-- {decision}, or "Nenhuma decis\xE3o nova"
+### New decisions made during implementation
+- {decision}, or "No new decision"
 
-### D\xFAvidas em aberto
-{anything unresolved, or "Nenhuma"}
+### Open questions
+{anything unresolved, or "None"}
 
 ---
-Se algo n\xE3o estiver claro, PARE e pergunte \u2014 n\xE3o prossiga chutando.
+If anything is unclear, STOP and ask \u2014 don't proceed on a guess.
 \`\`\`
 
 > "Story {STORY-KEY} is implemented. Switch to **Allye Orchestrator** (Ctrl+T \u2192 Allye Orchestrator) and paste the handover above \u2014 it'll dispatch review and handle status from here."

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "allye-opencode",
-  "version": "1.2.4",
+  "version": "1.2.6",
   "description": "Allye multi-agent plugin for OpenCode — planning, building, reviewing, and delivering with structured workflows",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",