@hanzlaa/rcode 3.6.16 → 4.0.0

package/rihal/workflows/memory-init.md

@@ -1,106 +0,0 @@
-# Workflow: rcode-memory-init
-
-<purpose>
-Bootstrap the rcode Memory Bank for a project. Copies templates from `rihal/templates/memory/` into `.rihal/memory/`, then asks 5 seed questions to populate context. Idempotent: re-running on an initialised project produces a gap report instead of overwriting.
-</purpose>
-
-Bootstraps the rcode Memory Bank in the current project. Idempotent — re-running on an initialised project switches to a gap report instead of overwriting.
-
----
-
-## Inputs
-
-- **Project root** — current working directory; must contain a `.rihal/` folder (created by `rcode install`)
-- **Templates source** — `.rihal/templates/memory/` (copied from `rihal/templates/memory/` on install)
-
-## Preconditions
-
-- `.rihal/` exists (rcode is installed in this project)
-- `.rihal/templates/memory/` exists (templates ship with rcode)
-
-## Halt conditions
-
-- `.rihal/` missing → ask user to run `npx @hanzlaa/rcode install` first, then halt.
-- `.rihal/templates/memory/` missing → report bug, halt.
-- User cancels at any question → leave `.rihal/memory/` partially populated (whatever was seeded) and exit cleanly.
-
----
-
-## Steps
-
-### Step 1 — Detect existing Memory Bank
-
-```bash
-if [ -f ".rihal/memory/INDEX.md" ]; then
-  # Switch to gap-report mode
-  exit_with_gap_report
-fi
-```
-
-If `INDEX.md` exists:
-- List every file under `.rihal/memory/`
-- For each, count non-template lines (lines that don't start with `<!--` or contain `_(...)_` placeholders)
-- Print which files are empty / template-only and which are populated
-- Suggest `/rihal-memory-update` for surgical edits and exit
-
-### Step 2 — Copy templates
-
-```bash
-mkdir -p .rihal/memory
-cp -R .rihal/templates/memory/. .rihal/memory/
-```
-
-Preserves the directory structure. Includes `.gitkeep` files in empty subdirs.
-
-### Step 3 — Substitute placeholders
-
-Replace in every `*.md` file under `.rihal/memory/`:
-- `{{PROJECT_NAME}}` → derived from `package.json` `name`, fallback to directory basename
-- `{{INIT_DATE}}` → today's date in `YYYY-MM-DD` format
-
-### Step 4 — Five init questions
-
-Ask each via AskUserQuestion. Accept short answers; do not push for paragraphs.
-
-**Q1.** What is the one-sentence project goal? *(saved to `milestones/current.md` → Goal)*
-
-**Q2.** Primary stack — frontend / backend / database? *(parsed into `project/stack.md` Runtime table)*
-
-**Q3.** What is the current milestone name? *(saved to `milestones/current.md` → Milestone Name; default `M1 — Initial`)*
-
-**Q4.** Primary external stakeholder name and role? *(appended to `people/stakeholders.md`)*
-
-**Q5.** Any known production issue you'd warn a new teammate about today? *(appended to `incidents/known-issues.md`; "none" is acceptable)*
-
-### Step 5 — Update state.json
-
-Add or update the `memory_bank` block in `.rihal/state.json`:
-
-```json
-{
-  "memory_bank": {
-    "initialised_at": "<ISO datetime>",
-    "version": 1
-  }
-}
-```
-
-### Step 6 — Print summary
-
-Show:
-- File tree of `.rihal/memory/`
-- Files seeded vs files still empty
-- Suggested next command: `/rihal-memory-distill`
-
----
-
-## Post-conditions
-
-- `.rihal/memory/INDEX.md` exists with project name + date filled in
-- 4–5 of the seeded files have user-supplied content
-- `.rihal/state.json` records initialisation
-- The Diwan dashboard `/memory` route now renders content (Phase 3 dashboard work)
-
-## Reversibility
-
-Removing a botched init: `rm -rf .rihal/memory/` and `git checkout -- .rihal/state.json`. No external side effects.

package/rihal/workflows/memory-update.md

@@ -1,87 +0,0 @@
-# Workflow: rcode-memory-update
-
-<purpose>
-Append-only surgical update to a single Memory Bank file. Adds a decision, known issue, stakeholder note, or milestone update from current conversation context. Never rewrites, never deletes — pure append.
-</purpose>
-
-Append-only surgical update to a single Memory Bank file. Never rewrites, never deletes.
-
----
-
-## Inputs
-
-- **content** — the thing to remember, in plain English
-- **target** (optional) — explicit file path; if omitted, auto-detected from content
-
-## Preconditions
-
-- `.rihal/memory/` exists (run `/rihal-memory-init` first)
-
-## Halt conditions
-
-- `.rihal/memory/` missing → instruct user to init first
-- User asks to *change* (not append) an existing entry → refuse, redirect to direct file edit
-- Detected target file does not exist → report and halt (don't create new files in this workflow)
-
----
-
-## Steps
-
-### Step 1 — Auto-detect target
-
-Match keywords in the user's content against this routing table:
-
-| Signal | Target |
-|---|---|
-| "decision", "we chose", "ADR", "decided" | `project/decisions.md` |
-| "bug", "issue", "broken", "workaround" | `incidents/known-issues.md` |
-| "stakeholder", "client", "contact", "rep" | `people/stakeholders.md` |
-| "milestone", "sprint", "phase", "blocker" | `milestones/current.md` |
-| "stack", "framework", "library", "switched to" | `project/stack.md` |
-| "term", "glossary", "what does X mean" | `project/glossary.md` |
-| "team", "who owns", "engineer", "responsibility" | `people/team.md` |
-| "change record", "deployment", "rollback" | `change-records/` (creates new file) |
-
-If ambiguous, ask the user to pick from the top 2 candidates.
-
-### Step 2 — Confirm with user
-
-Show:
-- Target file path
-- Proposed entry, formatted to match the file's existing entry style
-- A "Apply / cancel / edit format" choice
-
-### Step 3 — Append
-
-For appendable files (`decisions.md`, `known-issues.md`, `stakeholders.md`, `team.md`, `glossary.md`):
-- Insert above the `<!-- Append new entries above this line -->` marker if present
-- Otherwise append to end of file with a blank line separator
-
-For `milestones/current.md`:
-- Allow only field-level updates (Goal, Active phase, Blockers, Recent decisions)
-- Replace the field's value, not the whole file
-
-For `change-records/`:
-- Create a new file `YYYYMMDD-NNN.md` where `NNN` is the next sequence number
-- Use the change-record template format
-
-### Step 4 — Stamp and verify
-
-- Add `YYYY-MM-DD` date (today, ISO format) to every appended entry
-- Print a diff preview (last 20 lines of the file) so the user can confirm the change landed
-
-### Step 5 — Suggest distillate refresh
-
-If the change was to `project/`, `milestones/current.md`, or `incidents/`, suggest `/rihal-memory-distill` to refresh distillates. Optional, not enforced.
-
----
-
-## Post-conditions
-
-- Exactly one file changed (or one new change-record file created)
-- File still parses as valid markdown
-- No content removed
-
-## Reversibility
-
-`git diff .rihal/memory/` shows exactly one append — easy to revert with `git checkout`.

package/rihal/workflows/milestone-summary.md

@@ -1,206 +0,0 @@
-# Workflow: rihal-milestone-summary
-
-<purpose>
-Generate a human-readable summary of the current or specified milestone, including all phases, decisions, outcomes, and lessons learned. Output can be Markdown (default) or PDF. This creates a narrative view of the entire milestone arc.
-</purpose>
-
-## Step 0 — Usage check
-
-If `$ARGUMENTS` contains only `--help` or `-h`:
-
-```
-/rihal-milestone-summary [--format=markdown|pdf] [--include-decisions]
-```
-
-**Examples:**
-```
-/rihal-milestone-summary
-/rihal-milestone-summary --format=pdf --include-decisions
-```
-
-STOP — do not proceed.
-
-## Step 1 — Parse arguments and locate milestone
-
-Extract flags:
-- `--format` → "markdown" (default) or "pdf"
-- `--include-decisions` → boolean
-
-Find active milestone (same logic as audit-milestone):
-- Check `.planning/current-milestone.txt`
-- Fallback to most recent in `.planning/milestones/`
-
-If not found:
-
-```
-⚠ No active milestone. Create one:
-
-/rihal-new-milestone <name>
-```
-
-STOP. Store path as `$MILESTONE_DIR`.
-
-## Step 2 — Load milestone artifacts
-
-Read:
-- `$MILESTONE_DIR/ROADMAP.md` → extract goals, phases, success criteria
-- `$MILESTONE_DIR/STATE.md` → extract decisions, blockers, workstreams
-- `$MILESTONE_DIR/REQUIREMENTS.md` → extract user stories, technical specs
-
-## Step 3 — Scan all phase summaries
-
-For each phase directory in `$MILESTONE_DIR/phases/`:
-- Read the phase name from directory name
-- Find and read SUMMARY.md
-- Extract: outcomes, metrics, key decisions, blockers
-- Store in `$PHASE_DATA` array ordered by phase number
-
-## Step 4 — Build narrative structure
-
-Create a timeline showing:
-
-```
-MILESTONE TIMELINE
-
-[Start Date] — Kickoff
-  - Initial goals (from ROADMAP)
-  - Key assumptions
-
-[Phase 1 Date] — Phase 1 Name
-  - Summary text (from SUMMARY.md)
-  - Key outcomes
-  - Decisions (if --include-decisions)
-
-[Phase 2 Date] — Phase 2 Name
-  [...]
-
-[End Date] — Completion
-  - Final metrics
-  - Overall success assessment
-```
-
-## Step 5 — Compile summary document
-
-Generate Markdown (or PDF-source) output:
-
-```markdown
-# {MILESTONE_NAME} — Milestone Summary
-
-**Duration:** [start] — [end]
-**Status:** [PLANNING | IN_PROGRESS | COMPLETED]
-
-## Overview
-
-{one paragraph overview of what this milestone aimed to accomplish}
-
-## Original Goals
-
-- Goal 1: [text]
-- Goal 2: [text]
-- Goal 3: [text]
-
-## Milestone Timeline
-
-{timeline structure from Step 4}
-
-## Phase Summaries
-
-### Phase 1: {Name}
-**Duration:** [dates] | **Owner:** [person/team]
-
-{summary from SUMMARY.md, first 2-3 paragraphs}
-
-**Key Outcomes:**
-- Outcome 1
-- Outcome 2
-
-**Decisions Made:**
-{if --include-decisions, list from SUMMARY.md}
-
-### Phase 2: {Name}
-[...]
-
-## Overall Outcomes
-
-{aggregate achievements from all phases}
-
-## Metrics
-
-- Total phases: {count}
-- Duration: {count} days
-- Key deliverables: {count}
-
-## Decisions and Trade-offs
-
-{if --include-decisions, comprehensive decision log with rationales}
-
-## Lessons Learned
-
-- Lesson 1 (what went well)
-- Lesson 2 (what to improve next time)
-
-## Success Assessment
-
-[Did we meet the original goals? What did we learn?]
-
-## Appendix
-
-- [Link to ROADMAP.md]
-- [Link to STATE.md]
-- [Link to archive location]
-```
-
-## Step 6 — Handle PDF export (if requested)
-
-If `--format=pdf`:
-
-1. Convert Markdown to PDF using a simple text-to-PDF approach
-   (or provide instructions for user to use pandoc/wkhtmltopdf if needed)
-2. Save as `.planning/milestone-summary-{TIMESTAMP}.pdf`
-
-Otherwise, save as `.planning/milestone-summary-{TIMESTAMP}.md`
-
-## Step 7 — Report
-
-Print:
-
-```
-✓ Summary generated
-  Format: {format}
-  Location: {file_path}
-  
-View it:
-  cat {file_path}
-```
-
-## Success Criteria
-
-- Milestone summary created covering all phases
-- Narrative structure (timeline, outcomes, decisions)
-- Output format matches requested (Markdown or PDF)
-- File saved to `.planning/milestone-summary-*.{md|pdf}`
-- User can easily read and share the document
-
-## On Error
-
-If no phase summaries found:
-
-```
-⚠ No phase summaries in milestone. Execute phases first:
-
-/rihal-plan <phase description>
-/rihal-execute <plan-artifact>
-```
-
-If ROADMAP.md missing:
-
-```
-⚠ ROADMAP.md missing. Cannot generate summary without original goals.
-```
-
-If PDF conversion fails:
-
-```
-⚠ PDF conversion failed. Saving as Markdown instead:
-  {file_path}
-```