ariadna 1.3.0 → 2.0.0

data/data/ariadna/workflows/progress.md

@@ -1,385 +1,29 @@
-<purpose>
-Check project progress, summarize recent work and what's ahead, then intelligently route to the next action — either executing an existing plan or creating the next one. Provides situational awareness before continuing work.
-</purpose>
-
-<required_reading>
-Read all files referenced by the invoking prompt's execution_context before starting.
-</required_reading>
-
-<process>
+---
+name: progress
+description: Check project progress and route to the next action — absorbs resume-project and pause-work.
+---
 
-<step name="init_context">
-**Load progress context (with file contents to avoid redundant reads):**
+## Goal
+Give instant situational awareness (recent work, current position, blockers) then route precisely to the next command — execute an existing plan, create the next one, fix UAT gaps, complete a milestone, or start the next milestone cycle. Also handles session pause (create `.continue-here.md`) and resume (restore from checkpoint).
 
+## Context Loading
 ```bash
 INIT=$(ariadna-tools init progress --include state,roadmap,project,config)
-```
-
-Extract from init JSON: `project_exists`, `roadmap_exists`, `state_exists`, `phases`, `current_phase`, `next_phase`, `milestone_version`, `completed_count`, `phase_count`, `paused_at`.
-
-**File contents (from --include):** `state_content`, `roadmap_content`, `project_content`, `config_content`. These are null if files don't exist.
-
-If `project_exists` is false (no `.ariadna_planning/` directory):
-
-```
-No planning structure found.
-
-Run /ariadna:new-project to start a new project.
-```
-
-Exit.
-
-If missing STATE.md: suggest `/ariadna:new-project`.
-
-**If ROADMAP.md missing but PROJECT.md exists:**
-
-This means a milestone was completed and archived. Go to **Route F** (between milestones).
-
-If missing both ROADMAP.md and PROJECT.md: suggest `/ariadna:new-project`.
-</step>
-
-<step name="load">
-**Use project context from INIT:**
-
-All file contents are already loaded via `--include` in init_context step:
-- `state_content` — living memory (position, decisions, issues)
-- `roadmap_content` — phase structure and objectives
-- `project_content` — current state (What This Is, Core Value, Requirements)
-- `config_content` — settings (model_profile, workflow toggles)
-
-No additional file reads needed.
-</step>
-
-<step name="analyze_roadmap">
-**Get comprehensive roadmap analysis (replaces manual parsing):**
-
-```bash
 ROADMAP=$(ariadna-tools roadmap analyze)
 ```
+Parse from init: `project_exists`, `roadmap_exists`, `paused_at`. If `project_exists` is false, suggest `/ariadna:new-project` and exit. If ROADMAP.md missing but PROJECT.md exists, route to **between milestones** (suggest `/ariadna:new-milestone`). Read 2-3 most recent SUMMARY.md files for recent-work context.
 
-This returns structured JSON with:
-- All phases with disk status (complete/partial/planned/empty/no_directory)
-- Goal and dependencies per phase
-- Plan and summary counts per phase
-- Aggregated stats: total plans, summaries, progress percent
-- Current and next phase identification
-
-Use this instead of manually reading/parsing ROADMAP.md.
-</step>
-
-<step name="recent">
-**Gather recent work context:**
-
-- Find the 2-3 most recent SUMMARY.md files
-- Use `summary-extract` for efficient parsing:
-  ```bash
-  ariadna-tools summary-extract <path> --fields one_liner
-  ```
-- This shows "what we've been working on"
-  </step>
-
-<step name="position">
-**Parse current position from init context and roadmap analysis:**
-
-- Use `current_phase` and `next_phase` from roadmap analyze
-- Use phase-level `has_context` and `has_research` flags from analyze
-- Note `paused_at` if work was paused (from init context)
-- Count pending todos: use `init todos` or `list-todos`
-- Check for active debug sessions: `ls .ariadna_planning/debug/*.md 2>/dev/null | grep -v resolved | wc -l`
-  </step>
-
-<step name="report">
-**Generate progress bar from ariadna-tools, then present rich status report:**
-
-```bash
-# Get formatted progress bar
-PROGRESS_BAR=$(ariadna-tools progress bar --raw)
-```
-
-Present:
-
-```
-# [Project Name]
-
-**Progress:** {PROGRESS_BAR}
-**Profile:** [quality/balanced/budget]
-
-## Recent Work
-- [Phase X, Plan Y]: [what was accomplished - 1 line from summary-extract]
-- [Phase X, Plan Z]: [what was accomplished - 1 line from summary-extract]
-
-## Current Position
-Phase [N] of [total]: [phase-name]
-Plan [M] of [phase-total]: [status]
-CONTEXT: [✓ if has_context | - if not]
-
-## Key Decisions Made
-- [decision 1 from STATE.md]
-- [decision 2]
-
-## Blockers/Concerns
-- [any blockers or concerns from STATE.md]
-
-## Pending Todos
-- [count] pending — /ariadna:check-todos to review
-
-## Active Debug Sessions
-- [count] active — /ariadna:debug to continue
-(Only show this section if count > 0)
-
-## What's Next
-[Next phase/plan objective from roadmap analyze]
-```
-
-</step>
-
-<step name="route">
-**Determine next action based on verified counts.**
-
-**Step 1: Count plans, summaries, and issues in current phase**
-
-List files in the current phase directory:
-
-```bash
-ls -1 .ariadna_planning/phases/[current-phase-dir]/*-PLAN.md 2>/dev/null | wc -l
-ls -1 .ariadna_planning/phases/[current-phase-dir]/*-SUMMARY.md 2>/dev/null | wc -l
-ls -1 .ariadna_planning/phases/[current-phase-dir]/*-UAT.md 2>/dev/null | wc -l
-```
-
-State: "This phase has {X} plans, {Y} summaries."
-
-**Step 1.5: Check for unaddressed UAT gaps**
-
-Check for UAT.md files with status "diagnosed" (has gaps needing fixes).
-
-```bash
-# Check for diagnosed UAT with gaps
-grep -l "status: diagnosed" .ariadna_planning/phases/[current-phase-dir]/*-UAT.md 2>/dev/null
-```
-
-Track:
-- `uat_with_gaps`: UAT.md files with status "diagnosed" (gaps need fixing)
-
-**Step 2: Route based on counts**
-
-| Condition | Meaning | Action |
-|-----------|---------|--------|
-| uat_with_gaps > 0 | UAT gaps need fix plans | Go to **Route E** |
-| summaries < plans | Unexecuted plans exist | Go to **Route A** |
-| summaries = plans AND plans > 0 | Phase complete | Go to Step 3 |
-| plans = 0 | Phase not yet planned | Go to **Route B** |
-
----
-
-**Route A: Unexecuted plan exists**
-
-Find the first PLAN.md without matching SUMMARY.md.
-Read its `<objective>` section.
-
-```
----
-
-## ▶ Next Up
-
-**{phase}-{plan}: [Plan Name]** — [objective summary from PLAN.md]
-
-`/ariadna:execute-phase {phase}`
-
-<sub>`/clear` first → fresh context window</sub>
-
----
-```
-
----
-
-**Route B: Phase needs planning**
-
-Check if `{phase}-CONTEXT.md` exists in phase directory.
-
-**If CONTEXT.md exists:**
-
-```
----
-
-## ▶ Next Up
-
-**Phase {N}: {Name}** — {Goal from ROADMAP.md}
-<sub>✓ Context gathered, ready to plan</sub>
-
-`/ariadna:plan-phase {phase-number}`
-
-<sub>`/clear` first → fresh context window</sub>
-
----
-```
-
-**If CONTEXT.md does NOT exist:**
-
-```
----
-
-## ▶ Next Up
-
-**Phase {N}: {Name}** — {Goal from ROADMAP.md}
-
-`/ariadna:discuss-phase {phase}` — gather context and clarify approach
-
-<sub>`/clear` first → fresh context window</sub>
-
----
-
-**Also available:**
-- `/ariadna:plan-phase {phase}` — skip discussion, plan directly
-- `/ariadna:list-phase-assumptions {phase}` — see Claude's assumptions
-
----
-```
-
----
-
-**Route E: UAT gaps need fix plans**
-
-UAT.md exists with gaps (diagnosed issues). User needs to plan fixes.
-
-```
----
-
-## ⚠ UAT Gaps Found
-
-**{phase}-UAT.md** has {N} gaps requiring fixes.
-
-`/ariadna:plan-phase {phase} --gaps`
-
-<sub>`/clear` first → fresh context window</sub>
-
----
-
-**Also available:**
-- `/ariadna:execute-phase {phase}` — execute phase plans
-- `/ariadna:verify-work {phase}` — run more UAT testing
-
----
-```
-
----
-
-**Step 3: Check milestone status (only when phase complete)**
-
-Read ROADMAP.md and identify:
-1. Current phase number
-2. All phase numbers in the current milestone section
-
-Count total phases and identify the highest phase number.
-
-State: "Current phase is {X}. Milestone has {N} phases (highest: {Y})."
-
-**Route based on milestone status:**
-
-| Condition | Meaning | Action |
-|-----------|---------|--------|
-| current phase < highest phase | More phases remain | Go to **Route C** |
-| current phase = highest phase | Milestone complete | Go to **Route D** |
-
----
-
-**Route C: Phase complete, more phases remain**
-
-Read ROADMAP.md to get the next phase's name and goal.
-
-```
----
-
-## ✓ Phase {Z} Complete
-
-## ▶ Next Up
-
-**Phase {Z+1}: {Name}** — {Goal from ROADMAP.md}
-
-`/ariadna:discuss-phase {Z+1}` — gather context and clarify approach
-
-<sub>`/clear` first → fresh context window</sub>
-
----
-
-**Also available:**
-- `/ariadna:plan-phase {Z+1}` — skip discussion, plan directly
-- `/ariadna:verify-work {Z}` — user acceptance test before continuing
-
----
-```
-
----
-
-**Route D: Milestone complete**
-
-```
----
-
-## 🎉 Milestone Complete
-
-All {N} phases finished!
-
-## ▶ Next Up
-
-**Complete Milestone** — archive and prepare for next
-
-`/ariadna:complete-milestone`
-
-<sub>`/clear` first → fresh context window</sub>
-
----
-
-**Also available:**
-- `/ariadna:verify-work` — user acceptance test before completing milestone
-
----
-```
-
----
-
-**Route F: Between milestones (ROADMAP.md missing, PROJECT.md exists)**
-
-A milestone was completed and archived. Ready to start the next milestone cycle.
-
-Read MILESTONES.md to find the last completed milestone version.
-
-```
----
-
-## ✓ Milestone v{X.Y} Complete
-
-Ready to plan the next milestone.
-
-## ▶ Next Up
-
-**Start Next Milestone** — questioning → research → requirements → roadmap
-
-`/ariadna:new-milestone`
-
-<sub>`/clear` first → fresh context window</sub>
-
----
-```
-
-</step>
-
-<step name="edge_cases">
-**Handle edge cases:**
-
-- Phase complete but next phase not planned → offer `/ariadna:plan-phase [next]`
-- All work complete → offer milestone completion
-- Blockers present → highlight before offering to continue
-- Handoff file exists → mention it, offer `/ariadna:resume-work`
-  </step>
-
-</process>
+## Constraints
+- Never take action automatically — always present status first, then route with a command suggestion
+- Routing priority: UAT gaps → unexecuted plans → plan the current phase → complete milestone → new milestone
+- Pause mode: if user says "pause" or "stop", write `.ariadna_planning/phases/{dir}/.continue-here.md` with full work state and commit as WIP
+- Resume mode: detect `.continue-here.md` or incomplete PLAN (no matching SUMMARY) and surface as "Incomplete work detected" before routing
+- Use `ariadna-tools progress bar --raw` for the visual progress bar
 
-<success_criteria>
+## Success Criteria
+- Status report shows: progress bar, recent work, current position, decisions, blockers, pending todos
+- Routing suggestion is unambiguous — one primary command with `/clear` reminder
+- Pause/resume produces or consumes `.continue-here.md` with specific enough context for a fresh session
 
-- [ ] Rich context provided (recent work, decisions, issues)
-- [ ] Current position clear with visual progress
-- [ ] What's next clearly explained
-- [ ] Smart routing: /ariadna:execute-phase if plans exist, /ariadna:plan-phase if not
-- [ ] User confirms before any action
-- [ ] Seamless handoff to appropriate ariadna command
-      </success_criteria>
+## On Completion
+Present the "Next Up" block with the exact command to run. For pause, confirm handoff file location and show `/ariadna:progress` as the resume trigger.

data/data/ariadna/workflows/quick.md

@@ -1,230 +1,28 @@
-<purpose>
-Execute small, ad-hoc tasks with Ariadna guarantees (atomic commits, STATE.md tracking) while skipping optional agents (research, plan-checker, verifier). Quick mode spawns ariadna-planner (quick mode) + ariadna-executor(s), tracks tasks in `.ariadna_planning/quick/`, and updates STATE.md's "Quick Tasks Completed" table.
-</purpose>
-
-<required_reading>
-Read all files referenced by the invoking prompt's execution_context before starting.
-</required_reading>
-
-<process>
-**Step 1: Get task description**
-
-Prompt user interactively for the task description:
-
-```
-AskUserQuestion(
-  header: "Quick Task",
-  question: "What do you want to do?",
-  followUp: null
-)
-```
-
-Store response as `$DESCRIPTION`.
-
-If empty, re-prompt: "Please provide a task description."
-
----
-
-**Step 2: Initialize**
-
-```bash
-INIT=$(ariadna-tools init quick "$DESCRIPTION")
-```
-
-Parse JSON for: `planner_model`, `executor_model`, `commit_docs`, `next_num`, `slug`, `date`, `timestamp`, `quick_dir`, `task_dir`, `roadmap_exists`, `planning_exists`.
-
-**If `roadmap_exists` is false:** Error — Quick mode requires an active project with ROADMAP.md. Run `/ariadna:new-project` first.
-
-Quick tasks can run mid-phase - validation only checks ROADMAP.md exists, not phase status.
-
 ---
-
-**Step 3: Create task directory**
-
-```bash
-mkdir -p "${task_dir}"
-```
-
+name: quick
+description: Execute a small ad-hoc task with Ariadna guarantees — atomic commits and STATE.md tracking — without the full phase workflow.
 ---
 
-**Step 4: Create quick task directory**
-
-Create the directory for this quick task:
+## Goal
+Run a focused, self-contained task outside the planned phase cycle. Spawns a planner (quick mode, 1-3 tasks) and an executor, commits artifacts, and records the task in STATE.md's "Quick Tasks Completed" table.
 
+## Context Loading
 ```bash
-QUICK_DIR=".ariadna_planning/quick/${next_num}-${slug}"
-mkdir -p "$QUICK_DIR"
-```
-
-Report to user:
-```
-Creating quick task ${next_num}: ${DESCRIPTION}
-Directory: ${QUICK_DIR}
-```
-
-Store `$QUICK_DIR` for use in orchestration.
-
----
-
-**Step 5: Spawn planner (quick mode)**
-
-Spawn ariadna-planner with quick mode context:
-
-```
-Task(
-  prompt="
-<planning_context>
-
-**Mode:** quick
-**Directory:** ${QUICK_DIR}
-**Description:** ${DESCRIPTION}
-
-**Project State:**
-@.ariadna_planning/STATE.md
-
-</planning_context>
-
-<constraints>
-- Create a SINGLE plan with 1-3 focused tasks
-- Quick tasks should be atomic and self-contained
-- No research phase, no checker phase
-- Target ~30% context usage (simple, focused)
-</constraints>
-
-<output>
-Write plan to: ${QUICK_DIR}/${next_num}-PLAN.md
-Return: ## PLANNING COMPLETE with plan path
-</output>
-",
-  subagent_type="ariadna-planner",
-  model="{planner_model}",
-  description="Quick plan: ${DESCRIPTION}"
-)
-```
-
-After planner returns:
-1. Verify plan exists at `${QUICK_DIR}/${next_num}-PLAN.md`
-2. Extract plan count (typically 1 for quick tasks)
-3. Report: "Plan created: ${QUICK_DIR}/${next_num}-PLAN.md"
-
-If plan not found, error: "Planner failed to create ${next_num}-PLAN.md"
-
----
-
-**Step 6: Spawn executor**
-
-Spawn ariadna-executor with plan reference:
-
-```
-Task(
-  prompt="
-Execute quick task ${next_num}.
-
-Plan: @${QUICK_DIR}/${next_num}-PLAN.md
-Project state: @.ariadna_planning/STATE.md
-
-<constraints>
-- Execute all tasks in the plan
-- Commit each task atomically
-- Create summary at: ${QUICK_DIR}/${next_num}-SUMMARY.md
-- Do NOT update ROADMAP.md (quick tasks are separate from planned phases)
-</constraints>
-",
-  subagent_type="ariadna-executor",
-  model="{executor_model}",
-  description="Execute: ${DESCRIPTION}"
-)
-```
-
-After executor returns:
-1. Verify summary exists at `${QUICK_DIR}/${next_num}-SUMMARY.md`
-2. Extract commit hash from executor output
-3. Report completion status
-
-**Known Claude Code bug (classifyHandoffIfNeeded):** If executor reports "failed" with error `classifyHandoffIfNeeded is not defined`, this is a Claude Code runtime bug — not a real failure. Check if summary file exists and git log shows commits. If so, treat as successful.
-
-If summary not found, error: "Executor failed to create ${next_num}-SUMMARY.md"
-
-Note: For quick tasks producing multiple plans (rare), spawn executors in parallel waves per execute-phase patterns.
-
----
-
-**Step 7: Update STATE.md**
-
-Update STATE.md with quick task completion record.
-
-**7a. Check if "Quick Tasks Completed" section exists:**
-
-Read STATE.md and check for `### Quick Tasks Completed` section.
-
-**7b. If section doesn't exist, create it:**
-
-Insert after `### Blockers/Concerns` section:
-
-```markdown
-### Quick Tasks Completed
-
-| # | Description | Date | Commit | Directory |
-|---|-------------|------|--------|-----------|
-```
-
-**7c. Append new row to table:**
-
-Use `date` from init:
-```markdown
-| ${next_num} | ${DESCRIPTION} | ${date} | ${commit_hash} | [${next_num}-${slug}](./quick/${next_num}-${slug}/) |
-```
-
-**7d. Update "Last activity" line:**
-
-Use `date` from init:
-```
-Last activity: ${date} - Completed quick task ${next_num}: ${DESCRIPTION}
-```
-
-Use Edit tool to make these changes atomically
-
----
-
-**Step 8: Final commit and completion**
-
-Stage and commit quick task artifacts:
-
-```bash
-ariadna-tools commit "docs(quick-${next_num}): ${DESCRIPTION}" --files ${QUICK_DIR}/${next_num}-PLAN.md ${QUICK_DIR}/${next_num}-SUMMARY.md .ariadna_planning/STATE.md
-```
-
-Get final commit hash:
-```bash
-commit_hash=$(git rev-parse --short HEAD)
-```
-
-Display completion output:
+INIT=$(ariadna-tools init quick "$DESCRIPTION")
 ```
----
-
-Ariadna > QUICK TASK COMPLETE
+Ask the user for `$DESCRIPTION` first via AskUserQuestion if not provided. Parse: `planner_model`, `executor_model`, `next_num`, `slug`, `task_dir`, `roadmap_exists`. If `roadmap_exists` is false, error — run `/ariadna:new-project` first.
 
-Quick Task ${next_num}: ${DESCRIPTION}
-
-Summary: ${QUICK_DIR}/${next_num}-SUMMARY.md
-Commit: ${commit_hash}
-
----
-
-Ready for next task: /ariadna:quick
-```
+## Constraints
+- One plan per quick task (1-3 focused tasks inside the plan); no research, no plan-checker, no verifier
+- Executor must NOT update ROADMAP.md — quick tasks are separate from planned phases
+- Task directory: `.ariadna_planning/quick/{NNN}-{slug}/`; numbered sequentially (001, 002…)
+- Both `{NNN}-PLAN.md` and `{NNN}-SUMMARY.md` must exist before STATE.md update
+- If executor returns `classifyHandoffIfNeeded` error, check for summary file + git log before treating as failure
 
-</process>
+## Success Criteria
+- `{NNN}-PLAN.md` and `{NNN}-SUMMARY.md` exist in the task directory
+- STATE.md "Quick Tasks Completed" table updated with task row and "Last activity" line
+- All artifacts committed atomically
 
-<success_criteria>
-- [ ] ROADMAP.md validation passes
-- [ ] User provides task description
-- [ ] Slug generated (lowercase, hyphens, max 40 chars)
-- [ ] Next number calculated (001, 002, 003...)
-- [ ] Directory created at `.ariadna_planning/quick/NNN-slug/`
-- [ ] `${next_num}-PLAN.md` created by planner
-- [ ] `${next_num}-SUMMARY.md` created by executor
-- [ ] STATE.md updated with quick task row
-- [ ] Artifacts committed
-</success_criteria>
+## On Completion
+Display task number, description, summary path, and commit hash. Offer `/ariadna:quick` for the next ad-hoc task.

data/data/ariadna/workflows/roadmap-ops.md

@@ -0,0 +1,28 @@
+---
+name: roadmap-ops
+description: Modify the roadmap structure — add a phase at the end, insert a decimal phase between existing phases, or remove an unstarted phase with renumbering.
+---
+
+## Goal
+Apply structural changes to ROADMAP.md cleanly and atomically. Delegates all heavy lifting (directory creation/deletion, renumbering, ROADMAP.md edits) to `ariadna-tools phase {op}` and records the change in STATE.md's "Roadmap Evolution" section.
+
+## Context Loading
+```bash
+INIT=$(ariadna-tools init phase-op "${target_phase_or_0}")
+```
+Parse: `roadmap_exists`, `phase_found`, `phase_dir`. If `roadmap_exists` is false, error and exit. Determine operation from `$ARGUMENTS`: `add <description>`, `insert <after_phase> <description>`, or `remove <phase_number>`.
+
+## Constraints
+- **add**: appends a new integer phase (max + 1) at end of milestone; requires description; use for planned work
+- **insert**: inserts a decimal phase (e.g., 72.1) immediately after an existing integer phase; requires `<after_phase>` and description; marks as `(INSERTED)` in ROADMAP.md; use for urgent mid-milestone work only
+- **remove**: only future phases (target > current); requires user confirmation before executing; use `--force` only if user explicitly confirms removal of a phase with existing SUMMARY.md files; the git commit is the historical record — do NOT add redundant notes to STATE.md
+- All three operations commit immediately after execution
+- Do NOT create plans during these operations — that is `/ariadna:plan-phase`'s job
+
+## Success Criteria
+- `ariadna-tools phase {add|insert|remove}` exits successfully with no errors
+- Phase directory created (add/insert) or deleted and subsequent phases renumbered (remove)
+- ROADMAP.md and STATE.md updated; changes committed
+
+## On Completion
+Display a summary of what changed (new phase number/directory, or removed phase + renumber count). For add/insert, suggest `/ariadna:plan-phase {N}` as next step. For remove, suggest `/ariadna:progress` to see the updated roadmap.