@hanzlaa/rcode 3.6.16 → 4.1.0

package/rihal/workflows/dev-story.md

@@ -1,437 +0,0 @@
-# Workflow: rihal-dev-story
-
-<purpose>
-Wrap a STORY.md file for AI-coder consumption. Produces:
-1. Full story context with acceptance criteria
-2. Explicit file paths for implementation
-3. Development checklist
-4. Entry gate via checklist-story-draft.md
-5. Exit gate via checklist-story-dod.md
-
-This workflow creates the execution prompt for a pair-programming session with an AI coder.
-</purpose>
-
-<required_reading>
-@.rihal/references/git-preflight.md
-</required_reading>
-
-
-## Step 0 — Parse Arguments
-
-**Supported argument forms (in order of precedence):**
-
-| Input | Example | Resolves to |
-|-------|---------|-------------|
-| Direct file path | `.planning/epics/EPIC-01.md` | Use as-is |
-| Epic + Story ID | `epic 1 story 3` or `EPIC-01.3` or `1.3` | `.planning/epics/EPIC-01.md` → Story 3 section |
-| Epic only | `epic 1` or `EPIC-01` or just `1` | `.planning/epics/EPIC-01.md` → list stories → pick |
-| No arguments | (empty) | Show usage, stop |
-
-**Parse logic:**
-
-```bash
-ARGS="$ARGUMENTS"
-EPIC_FILE=""
-STORY_NUMBER=""
-BRANCH_FLAG=false
-
-# Flag detection
-[[ "$ARGS" == *"--branch"* ]] && BRANCH_FLAG=true
-ARGS=$(echo "$ARGS" | sed 's/--branch[[:space:]]*//' | xargs)
-
-# Form 1: Direct .md path
-if [[ "$ARGS" == *.md ]]; then
-  EPIC_FILE="$ARGS"
-
-# Form 2: EPIC-01.3 or 1.3
-elif [[ "$ARGS" =~ ^[Ee][Pp][Ii][Cc]-?([0-9]+)\.([0-9]+)$ ]] || [[ "$ARGS" =~ ^([0-9]+)\.([0-9]+)$ ]]; then
-  EPIC_NUM=$(echo "$ARGS" | grep -oE '[0-9]+' | head -1)
-  STORY_NUMBER=$(echo "$ARGS" | grep -oE '[0-9]+' | tail -1)
-  EPIC_FILE=".planning/epics/EPIC-$(printf '%02d' $EPIC_NUM).md"
-
-# Form 3: "epic 1 story 3"
-elif [[ "$ARGS" =~ [Ee]pic[[:space:]]+([0-9]+)[[:space:]]+[Ss]tory[[:space:]]+([0-9]+) ]]; then
-  EPIC_NUM=$(echo "$ARGS" | grep -oiP '(?<=epic )\d+')
-  STORY_NUMBER=$(echo "$ARGS" | grep -oiP '(?<=story )\d+')
-  EPIC_FILE=".planning/epics/EPIC-$(printf '%02d' $EPIC_NUM).md"
-
-# Form 4: "epic 1" or "EPIC-01" or just "1"
-elif [[ "$ARGS" =~ ^[Ee]pic[[:space:]]+([0-9]+)$ ]] || [[ "$ARGS" =~ ^[Ee][Pp][Ii][Cc]-?([0-9]+)$ ]] || [[ "$ARGS" =~ ^([0-9]+)$ ]]; then
-  EPIC_NUM=$(echo "$ARGS" | grep -oE '[0-9]+' | head -1)
-  EPIC_FILE=".planning/epics/EPIC-$(printf '%02d' $EPIC_NUM).md"
-
-else
-  echo "Usage: /rihal-dev-story <epic-ref> [--branch]"
-  echo ""
-  echo "Examples:"
-  echo "  /rihal-dev-story epic 1             # list stories in EPIC-01"
-  echo "  /rihal-dev-story epic 1 story 3     # work on EPIC-01, story 3"
-  echo "  /rihal-dev-story EPIC-01.3          # same as above"
-  echo "  /rihal-dev-story 1.3 --branch       # with new git branch"
-  echo "  /rihal-dev-story .planning/epics/stories/1.3.md  # direct path"
-  echo ""
-  echo "Story files live in: .planning/epics/stories/"
-  STOP
-fi
-```
-
-**Resolve story file — stories live in `.planning/epics/stories/`:**
-
-```bash
-# Direct path form resolves immediately
-if [[ "$ARGS" == *.md ]]; then
-  STORY_FILE="$ARGS"
-else
-  STORY_FILE=".planning/epics/stories/${EPIC_NUM}.${STORY_NUMBER}.md"
-fi
-```
-
-**If no story number — list available stories for that epic and ask:**
-
-```bash
-if [[ -z "$STORY_NUMBER" ]]; then
-  AVAILABLE=$(ls .planning/epics/stories/${EPIC_NUM}.*.md 2>/dev/null)
-  if [[ -z "$AVAILABLE" ]]; then
-    echo "Error: No stories found for Epic ${EPIC_NUM} in .planning/epics/stories/"
-    echo "Run /rihal-create-epics-and-stories first."
-    STOP
-  fi
-  echo "Stories in Epic ${EPIC_NUM}:"
-  for f in $AVAILABLE; do
-    ID=$(basename "$f" .md)
-    TITLE=$(grep "^# Story" "$f" 2>/dev/null | sed 's/^# Story [0-9.]*: //')
-    EFF=$(grep "^\*\*Effort:\*\*" "$f" 2>/dev/null | sed 's/\*\*Effort:\*\* //')
-    STATUS=$(grep "^\*\*Status:\*\*" "$f" 2>/dev/null | sed 's/\*\*Status:\*\* //')
-    echo "  ${ID}  [${EFF}] [${STATUS}]  ${TITLE}"
-  done
-  # AskUserQuestion: "Which story number? (e.g. 1, 2, 3)"
-  # Set STORY_NUMBER, then STORY_FILE=".planning/epics/stories/${EPIC_NUM}.${STORY_NUMBER}.md"
-fi
-```
-
-**Validate and read story file — no extraction, it's a standalone file:**
-
-```bash
-if [[ ! -f "$STORY_FILE" ]]; then
-  echo "Error: Story file not found: $STORY_FILE"
-  echo "Available: $(ls .planning/epics/stories/${EPIC_NUM}.*.md 2>/dev/null | xargs -I{} basename {} .md | tr '\n' ' ')"
-  STOP
-fi
-
-STORY_CONTENT=$(cat "$STORY_FILE")
-STORY_ID="${EPIC_NUM}.${STORY_NUMBER}"
-STORY_TITLE=$(grep "^# Story" "$STORY_FILE" | sed "s/^# Story ${STORY_ID}: //")
-PERSONA=$(grep "^\*\*Persona:\*\*" "$STORY_FILE" | sed 's/\*\*Persona:\*\* //')
-EFFORT=$(grep "^\*\*Effort:\*\*" "$STORY_FILE" | sed 's/\*\*Effort:\*\* //')
-```
-
-**Branch creation (if `--branch` or `BRANCH_FLAG=true`):**
-
-```bash
-if [[ "$BRANCH_FLAG" == true ]]; then
-  STORY_SLUG=$(echo "$STORY_TITLE" | tr '[:upper:]' '[:lower:]' | sed 's/[^a-z0-9]/-/g' | sed 's/--*/-/g' | sed 's/^-\|-$//g' | cut -c1-40)
-  BRANCH_NAME="story/${EPIC_NUM}.${STORY_NUMBER}-${STORY_SLUG}"
-  git checkout -b "$BRANCH_NAME" 2>/dev/null || git checkout "$BRANCH_NAME"
-  echo "Branch: $BRANCH_NAME"
-fi
-```
-
-## Step 1 — Load Story & References
-
-```bash
-@.rihal/references/checklist-story-draft.md
-@.rihal/references/checklist-story-dod.md
-@.rihal/references/commit-conventions.md
-@.rihal/references/karpathy-guidelines.md
-```
-
-`STORY_CONTENT`, `STORY_ID`, `STORY_TITLE`, `PERSONA`, `EFFORT` are already set from Step 0.
-No re-read needed. Verify non-empty:
-
-```bash
-[[ -z "$STORY_ID" ]]    && echo "Error: Could not parse Story ID from epic file"    && STOP
-[[ -z "$STORY_TITLE" ]] && echo "Error: Could not parse Story title from epic file" && STOP
-```
-
-## Step 2 — Check Entry Gate
-
-Run story through checklist-story-draft.md:
-
-- ✓ Persona named
-- ✓ Action/outcome specified
-- ✓ 3+ acceptance criteria
-- ✓ Out-of-scope listed
-- ✓ Effort estimated
-
-Extract acceptance criteria from story:
-
-```bash
-CRITERIA=$(sed -n '/^## Acceptance Criteria/,/^## /p' "$STORY_FILE" | grep "^- \[ \]" | sed 's/^- \[ \] //')
-```
-
-If story fails checks, print error:
-
-```
-⚠️ Story does not pass entry gate:
-
-Missing: {failed checks}
-
-Fix the story file before proceeding.
-```
-
-Stop. Only proceed if ALL checks pass.
-
-## Step 3 — Generate Execution Context
-
-Produce a detailed context document that will be passed to an AI coder.
-
-**Detect related files (context for the coder):**
-
-```bash
-# Find relevant source files, tests, config
-PROJECT_ROOT=$(pwd)
-PACKAGE_JSON="$PROJECT_ROOT/package.json"
-README="$PROJECT_ROOT/README.md"
-PROJECT_MD="$PROJECT_ROOT/.planning/PROJECT.md"
-EPIC_FILE=$(echo "$STORY_CONTENT" | grep "^**Epic:**" | sed "s/^**Epic:** //" | sed "s/ —.*//" | xargs -I {} find .planning/epics -name "EPIC-*.md" -exec grep -l "^# Epic {}" {} \;)
-```
-
-## Step 4 — Create Dev Prompt
-
-Create `.planning/dev-sessions/{story-id}-dev-prompt.md`:
-
-```bash
-mkdir -p .planning/dev-sessions
-DEV_PROMPT_FILE=".planning/dev-sessions/${STORY_ID}-dev-prompt.md"
-```
-
-Content:
-
-```markdown
-# Development Session: {Story title}
-
-**Story ID:** {STORY_ID}
-
-**Persona:** {Persona}
-
-**Effort estimate:** {Size}
-
-**Status:** Ready for development
-
----
-
-## Story Context
-
-{Full story text from STORY.md, sections:}
-
-### User Story
-
-{Action: "As a X, I want to Y so that Z"}
-
-### Acceptance Criteria
-
-{All criteria with checkboxes for AI to mark as they implement}
-
-### Out of Scope
-
-{What NOT to do}
-
-### Dev Notes
-
-{Technical approach, risks, dependencies, testing strategy}
-
----
-
-## Project Context
-
-**Project name:** {from PROJECT.md}
-
-**Technology stack:** {from STACK.md or package.json}
-
-**Relevant files for this story:**
-
-{List of absolute paths that the coder should read/modify}
-
-**Dependencies:**
-
-{List stories/features that must be done first}
-
-**How to test locally:**
-
-{Commands to run tests, start dev server, etc.}
-
----
-
-## Implementation Checklist
-
-Before starting:
-- [ ] Read project README and STACK.md
-- [ ] Review existing tests for patterns
-- [ ] List files you'll create/modify in PR description
-
-During development:
-- [ ] Implement acceptance criteria one by one
-- [ ] Write tests alongside code
-- [ ] No console.log left in production code
-- [ ] Follow project commit conventions (see below)
-
-After implementation:
-- [ ] All acceptance criteria passing ✓
-- [ ] All edge cases tested ✓
-- [ ] Definition of Done checklist complete ✓
-- [ ] Create PR with story summary ✓
-
----
-
-## Commit Convention
-
-When committing code for this story, use:
-
-```
-{type}({scope}): {description}
-
-{optional body explaining why}
-```
-
-Example for this story:
-
-```
-feat(story-{N}.{M}): {story-specific description}
-
-{Why this change, what problem it solves}
-```
-
-See `.rihal/references/commit-conventions.md` for full rules.
-
----
-
-## Definition of Done
-
-This story is "Done" when all items in checklist-story-dod.md are checked:
-
-- [ ] **Acceptance Criteria:** All {count} criteria tested and passing
-- [ ] **Tests:** {unit tests, integration tests} written and passing
-- [ ] **Code Quality:** No lint errors, follows project patterns
-- [ ] **Commits:** Conventional Commits format, no AI attribution
-- [ ] **Handoff:** Story summary written, no blockers
-
----
-
-## Files to Create/Modify
-
-{Based on story, explicit paths for:}
-
-**Source files:**
-- {path/to/file1}
-- {path/to/file2}
-
-**Test files:**
-- {path/to/test1}
-- {path/to/test2}
-
-**Config/docs:**
-- {path/to/config}
-
----
-
-## Running This Story
-
-To execute with an AI coder:
-
-```bash
-/rihal-code .planning/dev-sessions/{story-id}-dev-prompt.md
-```
-
----
-
-**Created:** {ISO date}
-
-**Expected completion:** {date + effort estimate}
-
-**Story summary template** (for PR after implementation):
-
-```markdown
-## Summary
-
-Implemented {story title}.
-
-### Acceptance Criteria Met
-
-- ✓ Criterion 1
-- ✓ Criterion 2
-- ✓ Criterion 3
-
-### Testing
-
-Added {count} tests covering:
-- Happy path
-- Edge cases: {list}
-
-### Changes
-
-- {file1}: {what changed}
-- {file2}: {what changed}
-```
-```
-
-## Step 5 — Print Dev Session Summary
-
-Print the dev prompt path and next steps:
-
-```
-🎯 Dev Session Ready
-
-Story: {STORY_ID} — {Story title}
-Persona: {Persona}
-Effort: {Size}
-Acceptance Criteria: {count}
-
-Context file: {path to dev-prompt.md}
-
-Next: /rihal-code {path to dev-prompt.md}
-
-Or, continue the current session to:
-  - Ask clarifying questions
-  - Discuss edge cases
-  - Review dependencies
-```
-
-## Step 6 — Optional: Spawn AI Coder
-
-If user says "start coding" or "let's build", spawn the code execution workflow:
-
-```bash
-# User says "let's go" or "start", then:
-/rihal-code "$DEV_PROMPT_FILE"
-```
-
-Otherwise, offer:
-
-```
-Ready to code this story?
-
-/rihal-code {dev-prompt-file}
-```
-
-Stop and wait for user to proceed. Do NOT auto-spawn.
-
-## Errors
-
-- **Story file not found:** print error and exit
-- **Story fails entry gate:** print failures and ask user to fix story file
-- **Missing acceptance criteria:** cannot proceed; story is incomplete
-
-## Success Criteria
-
-- [ ] Task completed as requested
-- [ ] Output saved or reported
-- [ ] State updated if necessary
-- [ ] No errors encountered
-
-## On Error
-
-If arguments are invalid, missing files, or subagent fails:
-- Validate inputs match expected format
-- Check that required files exist
-- Retry with clearer arguments or report the specific error to the user
-

package/rihal/workflows/diagnose-issues.md

@@ -1,87 +0,0 @@
-<purpose>
-Diagnose issues surfaced during /rihal:verify-work. For each failed acceptance criterion, identify root cause, classify severity, and decide whether to fix in-flight or file as follow-up.
-
-Spawned by /rihal:verify-work when verification fails. Not typically called directly by users.
-</purpose>
-
-<required_reading>
-@.rihal/references/output-format.md
-@.rihal/references/common-bug-patterns.md
-@.rihal/references/verification-patterns.md
-</required_reading>
-
-<process>
-
-## 1. Receive failure list
-
-`/rihal:verify-work` passes a structured list of failures:
-
-```json
-[
-  {
-    "criterion": "Auth login completes in <2s",
-    "expected": "redirect to /dashboard within 2s of submit",
-    "actual": "redirected after 8s",
-    "evidence": "browser network log shows 6s spent on /api/me"
-  }
-]
-```
-
-## 2. For each failure — diagnose
-
-Parallel-spawn one investigator per failure. Each investigator:
-
-a. **Reproduce** locally using the verification steps from UAT.md.
-b. **Bisect** — narrow down which file/function/commit introduced the regression. Use `git log --since` + `git bisect` if needed.
-c. **Classify** — bug / config / docs / environment / spec.
-d. **Severity** — critical (blocks ship) / high (degrades core feature) / medium (workaround exists) / low (cosmetic).
-e. **Root cause** — one-sentence explanation.
-f. **Fix proposal** — one of:
-   - **In-flight** — small enough to fix in this phase before merging
-   - **Follow-up** — substantial; file an issue and proceed
-   - **Stop** — phase shouldn't ship; halt and re-plan
-
-## 3. Aggregate diagnosis
-
-Each investigator returns a structured diagnosis. The orchestrator collates:
-
-```
-Failed criteria: 3
-Diagnosis:
-  Critical: 1   (must fix before ship)
-  High:     1   (recommended fix in-flight)
-  Medium:   1   (file as follow-up, ship anyway)
-```
-
-## 4. Decide
-
-- All criticals fixable in-flight → loop into rihal-code-fixer with the diagnosis bundle.
-- Any critical not fixable in-flight → return STOP to verify-work; phase doesn't ship.
-- Otherwise → file follow-ups, return PROCEED to verify-work.
-
-## 5. Output
-
-`DIAGNOSIS.md` per failure, written to `.planning/phases/<NN>/diagnosis/<criterion-slug>.md`. Each contains:
-
-- Reproduction steps
-- Bisect result
-- Root cause
-- Severity + classification
-- Fix proposal + estimated effort
-
-Plus an aggregate `DIAGNOSIS-INDEX.md` summarizing all failures and the orchestrator's decision.
-
-</process>
-
-## Success Criteria
-
-- [ ] Every failed criterion has a DIAGNOSIS.md file
-- [ ] Each DIAGNOSIS.md has reproduction + root cause + fix proposal
-- [ ] Critical failures either get in-flight fix or halt the phase
-- [ ] Follow-up issues filed for medium/low items proceed without blocking ship
-
-## On Error
-
-- **Cannot reproduce** — mark diagnosis status `cannot-reproduce`. Often signals environment drift between verifier and dev. File as follow-up; do not block ship if all other criticals pass.
-- **Bisect inconclusive** — fall back to a hypothesis-driven investigation (read recent commits in the affected file, look for likely causes).
-- **Repair budget exhausted** — STOP. Return control to user with the full diagnosis bundle.

package/rihal/workflows/diff.md

@@ -1,80 +0,0 @@
-<purpose>
-Show all changes to .planning/ and .rihal/state.json between two commits, labeled by phase/plan ID.
-</purpose>
-
-## Step 0: Usage Check
-
-Parse arguments:
-- No args → diff HEAD~1 to HEAD (last commit vs parent)
-- `--last` → diff against the previous session's last commit (read from state.json `last_session_commit`)
-- `<sha1> <sha2>` → diff between explicit commits
-
-If invalid args: Show usage
-
-```
-Usage:
-  /rihal-diff              # Diff HEAD~1 to HEAD
-  /rihal-diff --last       # Diff against last session
-  /rihal-diff abc123 def456  # Diff between commits
-```
-
-## Step 1: Parse Arguments
-
-Extract SHAs:
-- If no args: `sha1 = HEAD~1`, `sha2 = HEAD`
-- If `--last`: Read `.rihal/state.json`, extract `sessions[].commit`, use oldest in current session as sha1, HEAD as sha2
-- If explicit SHAs: Use as provided
-
-## Step 2: Run Git Diff
-
-```bash
-git diff $sha1 $sha2 -- .planning/ .rihal/state.json
-```
-
-Capture output.
-
-If no changes: Return `No changes between {sha1}..{sha2}`
-
-## Step 3: Label Each Diff Hunk
-
-For each file in diff output:
-
-1. Extract filename: `.planning/phases/01-foundation/01-1-SPRINT.md`
-2. Read that file's YAML frontmatter (if .md): extract phase/plan ID
-3. Prefix the hunk with: `Phase {id} — {filename}`
-4. Show the diff +/- lines
-
-For `.rihal/state.json`: Show raw diff (no frontmatter parsing)
-
-Example output:
-
-```
-Phase 01-01 — .planning/phases/01-foundation/01-1-SPRINT.md
-  @@ -5,3 +5,4 @@
-  - old line
-  + new line
-
-State changes — .rihal/state.json
-  @@ -12,2 +12,3 @@
-  - "status": "pending"
-  + "status": "completed"
-```
-
-## Success Criteria
-
-- [ ] Arguments parsed correctly
-- [ ] Git diff executed
-- [ ] Hunks labeled with phase/plan ID
-- [ ] Output is readable and scannable
-
-## On Error
-
-- Git error (invalid SHAs, not a repo) → Show git error
-- state.json missing for `--last` → "Cannot find session info. Use explicit SHAs or no args."
-- No changes → Return message "No changes between {shas}"
-
-## On Completion
-
-/rihal-plan {phase} — plan fixes for changes seen in the diff
-/rihal-execute {phase} — execute the phase
-/rihal-progress — see full roadmap status