@rayburst/cc 1.0.24 → 1.0.25

package/commands/rb/implement.md

@@ -48,21 +48,6 @@ Examples:
 
 ## Workflow
 
-### Step 0: Check for Resume State
-
-Before anything else, check if a previous `rb:implement` session was interrupted:
-
-1. Run `ls .claude/rb-sessions/*.md 2>/dev/null` (via Bash).
-2. **If a `cardId` was passed as input**, check for `.claude/rb-sessions/<cardId>.md` specifically:
-   - If it exists, read it and follow the `## Resume Instructions` section exactly.
-   - If it does not exist but other session files are present, proceed normally from Step 1 (start fresh for this card).
-3. **If no `cardId` was passed** and session files exist:
-   - If exactly one file: read it and follow its `## Resume Instructions` exactly.
-   - If multiple files: read each to get `sessionTitle` and `cardId`, list them to the user, and ask which to resume.
-4. If no session files exist, proceed normally from Step 1.
-
----
-
 ### Step 0b: Resolve MCP Prefix
 
 Read `.claude/rb-config.md` and parse the `## MCP Role Assignments` table. Find the row where `Role` is `engineer` and read its `MCP Server Name`.
@@ -175,7 +160,7 @@ Then in Step 6 (Enter Plan Mode), prepend a **"Fixing QA Failures"** section to
 
 If no prior failure comment or validation report is found, proceed normally.
 
-### Step 4: Move Card to `in-progress` and Write Early Session File
+### Step 4: Move Card to `in-progress`
 
 Before entering plan mode, move the card so the board reflects active work:
 
@@ -183,45 +168,6 @@ Before entering plan mode, move the card so the board reflects active work:
 <MCP_PREFIX>move_card({ cardId: "<cardId>", status: "in-progress" })
 ```
 
-Then **immediately** write an early session file so the card ID and intent survive a `/clear` or context compaction that might happen during plan approval:
-
-```bash
-mkdir -p .claude/rb-sessions
-cat > .claude/rb-sessions/<cardId>.md << 'RBEOF'
-# rb:implement Session
-
-## Session Info
-- **sessionTitle:** rb:implement — <card title>
-- **cardId:** <cardId>
-- **cardTitle:** <card title>
-- **startedAt:** <ISO timestamp>
-- **currentPhase:** Plan mode — plan not yet approved; re-enter plan mode and present it to the user
-
-## MCP Prefix
-`<MCP_PREFIX>`
-
-## Acceptance Criteria
-<list each criterion: - [criterionId] title — description>
-
-## Implementation Todos (in order)
-<list each todo item from the card's todo list, with checkbox: - [ ] todo text>
-
-## Resume Instructions
-
-IMPORTANT: You are resuming an interrupted `rb:implement` session. Context was cleared or compacted during plan approval. The card is already `in-progress`. Do NOT start over from Step 0. Execute the following immediately:
-
-1. Re-read the acceptance criteria and todos listed above.
-2. Enter plan mode (`EnterPlanMode`) and present the implementation plan to the user for approval.
-3. After user approves, post the plan as a card comment, then implement all todos in order.
-4. After ALL todos are complete and code is written, run:
-   `<MCP_PREFIX>move_card({ cardId: "<cardId>", status: "validation" })`
-5. Post an implementation summary comment:
-   `<MCP_PREFIX>add_comment({ cardId: "<cardId>", content: "## Implementation Complete\n\nReady for QA validation.\n\n### What was built\n<brief summary>\n\n### Files changed\n- <file>\n\n### Criteria coverage\n- <criterion>: satisfied via <explanation>" })`
-6. Delete this session file: `rm .claude/rb-sessions/<cardId>.md`
-7. Print: "## Implementation Complete: <card title>\n\nCard ID: <cardId>\nStatus: → validation\n\nRun /rb:validate-card <cardId> to run QA validation."
-RBEOF
-```
-
 ### Step 5: Conflict Detection
 
 Before planning, detect criteria in *other* active features that this implementation might break.
@@ -295,46 +241,6 @@ After the user approves the plan (via `ExitPlanMode`), post a concise summary to
 
 Keep the comment under 5000 characters. Use plain markdown prose — no raw code snippets or code fences with actual code (describe the approach, don't paste it).
 
-**Immediately after posting the plan comment**, update the session file — BEFORE writing any code. The early session file from Step 4 already exists; overwrite it now with the post-approval state so the resume instructions reflect that the plan is approved:
-
-Overwrite `.claude/rb-sessions/<cardId>.md` with the execution context:
-
-```bash
-cat > .claude/rb-sessions/<cardId>.md << 'RBEOF'
-# rb:implement Session
-
-## Session Info
-- **sessionTitle:** rb:implement — <card title>
-- **cardId:** <cardId>
-- **cardTitle:** <card title>
-- **startedAt:** <ISO timestamp>
-- **currentPhase:** Execute Implementation — plan approved, starting first todo item
-
-## MCP Prefix
-`<MCP_PREFIX>` (e.g. `mcp__rayburst-rb-engineer-780086__`)
-
-## Acceptance Criteria
-<list each criterion: - [criterionId] title — description>
-
-## Implementation Todos (in order)
-<list each todo item from the card's todo list, with checkbox: - [ ] todo text>
-
-## Resume Instructions
-
-IMPORTANT: You are resuming an interrupted `rb:implement` session. The plan was already approved and posted as a card comment. Do NOT re-enter plan mode. Do NOT ask the user what to do. Execute the following steps immediately:
-
-1. Run `<MCP_PREFIX>get_card({ cardId: "<cardId>" })` to get current card state.
-2. Check which todos are still incomplete. Continue from the first incomplete todo.
-3. Implement each remaining todo item in order — write the actual code changes.
-4. After ALL todos are complete and code is written, run:
-   `<MCP_PREFIX>move_card({ cardId: "<cardId>", status: "validation" })`
-5. Post an implementation summary comment:
-   `<MCP_PREFIX>add_comment({ cardId: "<cardId>", content: "## Implementation Complete\n\nReady for QA validation.\n\n### What was built\n<brief summary>\n\n### Files changed\n- <file>\n\n### Criteria coverage\n- <criterion>: satisfied via <explanation>" })`
-6. Delete this session file: `rm .claude/rb-sessions/<cardId>.md`
-7. Print: "## Implementation Complete: <card title>\n\nCard ID: <cardId>\nStatus: → validation\n\nRun /rb:validate-card <cardId> to run QA validation."
-RBEOF
-```
-
 ### Step 8: Execute Implementation
 
 Switch to execute mode. Work through the implementation:
@@ -352,45 +258,6 @@ Switch to execute mode. Work through the implementation:
    cd rayburst-api && npm run check
    ```
 
-**At each major phase boundary** (e.g., after backend is complete, before starting frontend), rewrite `.claude/rb-sessions/<cardId>.md` with an updated `currentPhase` that contains the exact next action. Do NOT just sed one line — rewrite the whole file so the Resume Instructions stay complete. The `currentPhase` value should be precise enough that after compaction you know exactly what code to write next. Examples:
-- `Frontend phase — implement /legacy route in src/routes/legacy/index.tsx`
-- `Wrap-up — all todos done, next: move card to validation and post summary comment`
-
-```bash
-cat > .claude/rb-sessions/<cardId>.md << 'RBEOF'
-# rb:implement Session
-
-## Session Info
-- **sessionTitle:** rb:implement — <card title>
-- **cardId:** <cardId>
-- **cardTitle:** <card title>
-- **startedAt:** <ISO timestamp>
-- **currentPhase:** <precise description of exact next action>
-
-## MCP Prefix
-`<MCP_PREFIX>`
-
-## Acceptance Criteria
-<list each criterion: - [criterionId] title — description>
-
-## Remaining Todos
-<list only the NOT YET COMPLETE todos: - [ ] todo text>
-
-## Resume Instructions
-
-IMPORTANT: You are resuming an interrupted `rb:implement` session. Context was compacted and you lost track of the workflow. The plan was already approved. Do NOT re-enter plan mode. Do NOT ask the user what to do. Execute the following steps immediately:
-
-1. Your exact next action is: **<currentPhase>**
-2. Complete that action, then work through any remaining todos above in order.
-3. After ALL todos are done and code is written, run:
-   `<MCP_PREFIX>move_card({ cardId: "<cardId>", status: "validation" })`
-4. Post an implementation summary comment:
-   `<MCP_PREFIX>add_comment({ cardId: "<cardId>", content: "## Implementation Complete\n\nReady for QA validation.\n\n### What was built\n<brief summary>\n\n### Files changed\n- <file>\n\n### Criteria coverage\n- <criterion>: satisfied via <explanation>" })`
-5. Delete this session file: `rm .claude/rb-sessions/<cardId>.md`
-6. Print: "## Implementation Complete: <card title>\n\nCard ID: <cardId>\nStatus: → validation\n\nRun /rb:validate-card <cardId> to run QA validation."
-RBEOF
-```
-
 **At-risk criteria preservation**: If Step 5 flagged criteria from other features, verify after each relevant change that the behavior described in those criteria is still correct.
 
 ### Step 9: Verify Criteria
@@ -406,16 +273,12 @@ If any criterion is clearly not satisfied, loop back to Step 8 and fix it before
 
 ### Step 10: Move Card to `validation` and Print Summary
 
-Move the card to `validation` status and delete the session file:
+Move the card to `validation` status:
 
 ```
 <MCP_PREFIX>move_card({ cardId: "<cardId>", status: "validation" })
 ```
 
-```bash
-rm -f .claude/rb-sessions/<cardId>.md
-```
-
 Post a brief implementation summary comment:
 
 ```
@@ -515,7 +378,6 @@ Parse the `data:` line from the SSE response to extract the JSON result.
 - **Do NOT fix failing criteria during QA** — report them, return the card, and stop
 - **If conflict detection finds at-risk criteria, STOP and prompt** — do not silently proceed
 - **If user cancels after conflict detection, move card back to `ready`** before stopping
-- **Context auto-clean** — compact or delegate to subagent after each major implementation phase
 - **Implementation comments under 5000 characters** — no raw code in comment content
 - **Validation criterion comments under 500 characters** — plain prose only, no backticks
 - **Run `/rb:init` first** if `.claude/rb-config.md` is missing

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rayburst/cc",
-  "version": "1.0.24",
+  "version": "1.0.25",
   "description": "Rayburst slash commands for Claude Code — /rb:init, /rb:plan, /rb:sync, /rb:status, /rb:validate-feature, /rb:validate-card, /rb:implement, /rb:discover",
   "bin": {
     "rayburst-cc": "bin/install.js"