ariadna 1.2.0 → 1.2.2

data/data/ariadna/templates/research-project/SUMMARY.md

@@ -1,6 +1,6 @@
 # Research Summary Template
 
-Template for `.planning/research/SUMMARY.md` — executive summary of project research with roadmap implications for Ruby on Rails applications.
+Template for `.ariadna_planning/research/SUMMARY.md` — executive summary of project research with roadmap implications for Ruby on Rails applications.
 
 <template>
 

data/data/ariadna/templates/research.md

@@ -1,6 +1,6 @@
 # Research Template
 
-Template for `.planning/phases/XX-name/{phase}-RESEARCH.md` - comprehensive ecosystem research before planning.
+Template for `.ariadna_planning/phases/XX-name/{phase}-RESEARCH.md` - comprehensive ecosystem research before planning.
 
 **Purpose:** Document what Claude needs to know to implement a phase well - not just "which library" but "how do experts build this."
 
@@ -531,6 +531,6 @@ end
 - Code examples can be referenced in task actions
 
 **After creation:**
-- File lives in phase directory: `.planning/phases/XX-name/{phase}-RESEARCH.md`
+- File lives in phase directory: `.ariadna_planning/phases/XX-name/{phase}-RESEARCH.md`
 - Referenced during planning workflow
 - plan-phase loads it automatically when present

data/data/ariadna/templates/roadmap.md

@@ -1,6 +1,6 @@
 # Roadmap Template
 
-Template for `.planning/ROADMAP.md`.
+Template for `.ariadna_planning/ROADMAP.md`.
 
 ## Initial Roadmap (v1.0 Greenfield)
 

data/data/ariadna/templates/state.md

@@ -1,6 +1,6 @@
 # State Template
 
-Template for `.planning/STATE.md` — the project's living memory.
+Template for `.ariadna_planning/STATE.md` — the project's living memory.
 
 ---
 
@@ -11,7 +11,7 @@ Template for `.planning/STATE.md` — the project's living memory.
 
 ## Project Reference
 
-See: .planning/PROJECT.md (updated [date])
+See: .ariadna_planning/PROJECT.md (updated [date])
 
 **Core value:** [One-liner from PROJECT.md Core Value section]
 **Current focus:** [Current phase name]
@@ -56,7 +56,7 @@ Recent decisions affecting current work:
 
 ### Pending Todos
 
-[From .planning/todos/pending/ — ideas captured during sessions]
+[From .ariadna_planning/todos/pending/ — ideas captured during sessions]
 
 None yet.
 
@@ -147,7 +147,7 @@ Updated after each plan completion.
 
 **Pending Todos:** Ideas captured via /ariadna:add-todo
 - Count of pending todos
-- Reference to .planning/todos/pending/
+- Reference to .ariadna_planning/todos/pending/
 - Brief list if few, count if many (e.g., "5 pending todos — see /ariadna:check-todos")
 
 **Blockers/Concerns:** From "Next Phase Readiness" sections

data/data/ariadna/templates/summary.md

@@ -1,6 +1,6 @@
 # Summary Template
 
-Template for `.planning/phases/XX-name/{phase}-{plan}-SUMMARY.md` - phase completion documentation.
+Template for `.ariadna_planning/phases/XX-name/{phase}-{plan}-SUMMARY.md` - phase completion documentation.
 
 ---
 
@@ -38,6 +38,11 @@ patterns-established:
   - "Pattern 1: description"
   - "Pattern 2: description"
 
+requirements_covered:
+  - id: "REQ-ID"
+    description: "Requirement description"
+    evidence: "File/class implementing it"
+
 # Metrics
 duration: Xmin
 completed: YYYY-MM-DD
@@ -60,6 +65,12 @@ completed: YYYY-MM-DD
 - [Second key accomplishment]
 - [Third if applicable]
 
+## Requirements Covered
+| REQ-ID | Requirement | Evidence |
+|--------|-------------|----------|
+
+[Omit this section if no REQUIREMENTS.md exists or no requirements map to this phase/plan]
+
 ## Task Commits
 
 Each task was committed atomically:

data/data/ariadna/templates/user-setup.md

@@ -1,6 +1,6 @@
 # User Setup Template
 
-Template for `.planning/phases/XX-name/{phase}-USER-SETUP.md` - human-required configuration that Claude cannot automate.
+Template for `.ariadna_planning/phases/XX-name/{phase}-USER-SETUP.md` - human-required configuration that Claude cannot automate.
 
 **Purpose:** Document setup tasks that literally require human action - account creation, dashboard configuration, secret retrieval. Claude automates everything possible; this file captures only what remains.
 
@@ -307,4 +307,4 @@ curl -X POST http://localhost:3000/api/test-email \
 
 **Naming:** `{phase}-USER-SETUP.md` matches the phase number pattern.
 **Status tracking:** User marks checkboxes and updates status line when complete.
-**Searchability:** `grep -r "USER-SETUP" .planning/` finds all phases with user requirements.
+**Searchability:** `grep -r "USER-SETUP" .ariadna_planning/` finds all phases with user requirements.

data/data/ariadna/templates/verification-report.md

@@ -1,6 +1,6 @@
 # Verification Report Template
 
-Template for `.planning/phases/XX-name/{phase}-VERIFICATION.md` — phase goal verification results.
+Template for `.ariadna_planning/phases/XX-name/{phase}-VERIFICATION.md` — phase goal verification results.
 
 ---
 

data/data/ariadna/workflows/add-phase.md

@@ -34,7 +34,7 @@ INIT=$(ariadna-tools init phase-op "0")
 
 Check `roadmap_exists` from init JSON. If false:
 ```
-ERROR: No roadmap found (.planning/ROADMAP.md)
+ERROR: No roadmap found (.ariadna_planning/ROADMAP.md)
 Run /ariadna:new-project to initialize.
 ```
 Exit.
@@ -51,7 +51,7 @@ The CLI handles:
 - Finding the highest existing integer phase number
 - Calculating next phase number (max + 1)
 - Generating slug from description
-- Creating the phase directory (`.planning/phases/{NN}-{slug}/`)
+- Creating the phase directory (`.ariadna_planning/phases/{NN}-{slug}/`)
 - Inserting the phase entry into ROADMAP.md with Goal, Depends on, and Plans sections
 
 Extract from result: `phase_number`, `padded`, `name`, `slug`, `directory`.
@@ -60,7 +60,7 @@ Extract from result: `phase_number`, `padded`, `name`, `slug`, `directory`.
 <step name="update_project_state">
 Update STATE.md to reflect the new phase:
 
-1. Read `.planning/STATE.md`
+1. Read `.ariadna_planning/STATE.md`
 2. Under "## Accumulated Context" → "### Roadmap Evolution" add entry:
    ```
    - Phase {N} added: {description}
@@ -75,10 +75,10 @@ Present completion summary:
 ```
 Phase {N} added to current milestone:
 - Description: {description}
-- Directory: .planning/phases/{phase-num}-{slug}/
+- Directory: .ariadna_planning/phases/{phase-num}-{slug}/
 - Status: Not planned yet
 
-Roadmap updated: .planning/ROADMAP.md
+Roadmap updated: .ariadna_planning/ROADMAP.md
 
 ---
 

data/data/ariadna/workflows/add-todo.md

@@ -19,7 +19,7 @@ Extract from init JSON: `commit_docs`, `date`, `timestamp`, `todo_count`, `todos
 
 Ensure directories exist:
 ```bash
-mkdir -p .planning/todos/pending .planning/todos/done
+mkdir -p .ariadna_planning/todos/pending .ariadna_planning/todos/done
 ```
 
 Note existing areas from the todos array for consistency in infer_area step.
@@ -52,7 +52,7 @@ Infer area from file paths:
 | `src/db/*`, `database/*` | `database` |
 | `tests/*`, `__tests__/*` | `testing` |
 | `docs/*` | `docs` |
-| `.planning/*` | `planning` |
+| `.ariadna_planning/*` | `planning` |
 | `scripts/*`, `bin/*` | `tooling` |
 | No files or unclear | `general` |
 
@@ -62,7 +62,7 @@ Use existing area from step 2 if similar match exists.
 <step name="check_duplicates">
 ```bash
 # Search for key words from title in existing todos
-grep -l -i "[key words from title]" .planning/todos/pending/*.md 2>/dev/null
+grep -l -i "[key words from title]" .ariadna_planning/todos/pending/*.md 2>/dev/null
 ```
 
 If potential duplicate found:
@@ -86,7 +86,7 @@ Generate slug for the title:
 slug=$(ariadna-tools generate-slug "$title" --raw)
 ```
 
-Write to `.planning/todos/pending/${date}-${slug}.md`:
+Write to `.ariadna_planning/todos/pending/${date}-${slug}.md`:
 
 ```markdown
 ---
@@ -108,7 +108,7 @@ files:
 </step>
 
 <step name="update_state">
-If `.planning/STATE.md` exists:
+If `.ariadna_planning/STATE.md` exists:
 
 1. Use `todo_count` from init context (or re-run `init todos` if count changed)
 2. Update "### Pending Todos" under "## Accumulated Context"
@@ -118,7 +118,7 @@ If `.planning/STATE.md` exists:
 Commit the todo and any updated state:
 
 ```bash
-ariadna-tools commit "docs: capture todo - [title]" --files .planning/todos/pending/[filename] .planning/STATE.md
+ariadna-tools commit "docs: capture todo - [title]" --files .ariadna_planning/todos/pending/[filename] .ariadna_planning/STATE.md
 ```
 
 Tool respects `commit_docs` config and gitignore automatically.
@@ -128,7 +128,7 @@ Confirm: "Committed: docs: capture todo - [title]"
 
 <step name="confirm">
 ```
-Todo saved: .planning/todos/pending/[filename]
+Todo saved: .ariadna_planning/todos/pending/[filename]
 
   [title]
   Area: [area]

data/data/ariadna/workflows/audit-milestone.md

@@ -38,8 +38,8 @@ ariadna-tools phases list
 For each phase directory, read the VERIFICATION.md:
 
 ```bash
-cat .planning/phases/01-*/*-VERIFICATION.md
-cat .planning/phases/02-*/*-VERIFICATION.md
+cat .ariadna_planning/phases/01-*/*-VERIFICATION.md
+cat .ariadna_planning/phases/02-*/*-VERIFICATION.md
 # etc.
 ```
 
@@ -85,7 +85,7 @@ For each requirement in REQUIREMENTS.md mapped to this milestone:
 
 ## 6. Aggregate into v{version}-MILESTONE-AUDIT.md
 
-Create `.planning/v{version}-v{version}-MILESTONE-AUDIT.md` with:
+Create `.ariadna_planning/v{version}-v{version}-MILESTONE-AUDIT.md` with:
 
 ```yaml
 ---
@@ -135,7 +135,7 @@ Output this markdown directly (not as a code block). Route based on status:
 ## ✓ Milestone {version} — Audit Passed
 
 **Score:** {N}/{M} requirements satisfied
-**Report:** .planning/v{version}-MILESTONE-AUDIT.md
+**Report:** .ariadna_planning/v{version}-MILESTONE-AUDIT.md
 
 All requirements covered. Cross-phase integration verified. E2E flows complete.
 
@@ -158,7 +158,7 @@ All requirements covered. Cross-phase integration verified. E2E flows complete.
 ## ⚠ Milestone {version} — Gaps Found
 
 **Score:** {N}/{M} requirements satisfied
-**Report:** .planning/v{version}-MILESTONE-AUDIT.md
+**Report:** .ariadna_planning/v{version}-MILESTONE-AUDIT.md
 
 ### Unsatisfied Requirements
 
@@ -189,7 +189,7 @@ All requirements covered. Cross-phase integration verified. E2E flows complete.
 ───────────────────────────────────────────────────────────────
 
 **Also available:**
-- cat .planning/v{version}-MILESTONE-AUDIT.md — see full report
+- cat .ariadna_planning/v{version}-MILESTONE-AUDIT.md — see full report
 - /ariadna:complete-milestone {version} — proceed anyway (accept tech debt)
 
 ───────────────────────────────────────────────────────────────
@@ -201,7 +201,7 @@ All requirements covered. Cross-phase integration verified. E2E flows complete.
 ## ⚡ Milestone {version} — Tech Debt Review
 
 **Score:** {N}/{M} requirements satisfied
-**Report:** .planning/v{version}-MILESTONE-AUDIT.md
+**Report:** .ariadna_planning/v{version}-MILESTONE-AUDIT.md
 
 All requirements met. No critical blockers. Accumulated tech debt needs review.
 

data/data/ariadna/workflows/check-todos.md

@@ -92,7 +92,7 @@ If `files` field has entries, read and briefly summarize each.
 <step name="check_roadmap">
 Check for roadmap (can use init progress or directly check file existence):
 
-If `.planning/ROADMAP.md` exists:
+If `.ariadna_planning/ROADMAP.md` exists:
 1. Check if todo's area matches an upcoming phase
 2. Check if todo's files overlap with a phase's scope
 3. Note any match for action options
@@ -125,7 +125,7 @@ Use AskUserQuestion:
 <step name="execute_action">
 **Work on it now:**
 ```bash
-mv ".planning/todos/pending/[filename]" ".planning/todos/done/"
+mv ".ariadna_planning/todos/pending/[filename]" ".ariadna_planning/todos/done/"
 ```
 Update STATE.md todo count. Present problem/solution context. Begin work or ask how to proceed.
 
@@ -153,8 +153,8 @@ Re-run `init todos` to get updated count, then update STATE.md "### Pending Todo
 If todo was moved to done/, commit the change:
 
 ```bash
-git rm --cached .planning/todos/pending/[filename] 2>/dev/null || true
-ariadna-tools commit "docs: start work on todo - [title]" --files .planning/todos/done/[filename] .planning/STATE.md
+git rm --cached .ariadna_planning/todos/pending/[filename] 2>/dev/null || true
+ariadna-tools commit "docs: start work on todo - [title]" --files .ariadna_planning/todos/done/[filename] .ariadna_planning/STATE.md
 ```
 
 Tool respects `commit_docs` config and gitignore automatically.

data/data/ariadna/workflows/complete-milestone.md

@@ -8,9 +8,9 @@ Mark a shipped version (v1.0, v1.1, v2.0) as complete. Creates historical record
 
 1. templates/milestone.md
 2. templates/milestone-archive.md
-3. `.planning/ROADMAP.md`
-4. `.planning/REQUIREMENTS.md`
-5. `.planning/PROJECT.md`
+3. `.ariadna_planning/ROADMAP.md`
+4. `.ariadna_planning/REQUIREMENTS.md`
+5. `.ariadna_planning/PROJECT.md`
 
 </required_reading>
 
@@ -18,8 +18,8 @@ Mark a shipped version (v1.0, v1.1, v2.0) as complete. Creates historical record
 
 When a milestone completes:
 
-1. Extract full milestone details to `.planning/milestones/v[X.Y]-ROADMAP.md`
-2. Archive requirements to `.planning/milestones/v[X.Y]-REQUIREMENTS.md`
+1. Extract full milestone details to `.ariadna_planning/milestones/v[X.Y]-ROADMAP.md`
+2. Archive requirements to `.ariadna_planning/milestones/v[X.Y]-REQUIREMENTS.md`
 3. Update ROADMAP.md — replace milestone details with one-line summary
 4. Delete REQUIREMENTS.md (fresh one for next milestone)
 5. Perform full PROJECT.md evolution review
@@ -65,7 +65,7 @@ Total: {phase_count} phases, {total_plans} plans, all complete
 <config-check>
 
 ```bash
-cat .planning/config.json 2>/dev/null
+cat .ariadna_planning/config.json 2>/dev/null
 ```
 
 </config-check>
@@ -130,7 +130,7 @@ Extract one-liners from SUMMARY.md files using summary-extract:
 
 ```bash
 # For each phase in milestone, extract one-liner
-for summary in .planning/phases/*-*/*-SUMMARY.md; do
+for summary in .ariadna_planning/phases/*-*/*-SUMMARY.md; do
   ariadna-tools summary-extract "$summary" --fields one_liner | jq -r '.one_liner'
 done
 ```
@@ -163,7 +163,7 @@ Full PROJECT.md evolution review at milestone completion.
 Read all phase summaries:
 
 ```bash
-cat .planning/phases/*-*/*-SUMMARY.md
+cat .ariadna_planning/phases/*-*/*-SUMMARY.md
 ```
 
 **Full review checklist:**
@@ -297,7 +297,7 @@ Initial user testing showed demand for shape tools.
 
 <step name="reorganize_roadmap">
 
-Update `.planning/ROADMAP.md` — group completed milestone phases:
+Update `.ariadna_planning/ROADMAP.md` — group completed milestone phases:
 
 ```markdown
 # Roadmap: [Project Name]
@@ -348,7 +348,7 @@ ARCHIVE=$(ariadna-tools milestone complete "v[X.Y]" --name "[Milestone Name]")
 ```
 
 The CLI handles:
-- Creating `.planning/milestones/` directory
+- Creating `.ariadna_planning/milestones/` directory
 - Archiving ROADMAP.md to `milestones/v[X.Y]-ROADMAP.md`
 - Archiving REQUIREMENTS.md to `milestones/v[X.Y]-REQUIREMENTS.md` with archive header
 - Moving audit file to milestones if it exists
@@ -357,9 +357,9 @@ The CLI handles:
 
 Extract from result: `version`, `date`, `phases`, `plans`, `tasks`, `accomplishments`, `archived`.
 
-Verify: `✅ Milestone archived to .planning/milestones/`
+Verify: `✅ Milestone archived to .ariadna_planning/milestones/`
 
-**Note:** Phase directories (`.planning/phases/`) are NOT deleted — they accumulate across milestones as raw execution history. Phase numbering continues (v1.0 phases 1-4, v1.1 phases 5-8, etc.).
+**Note:** Phase directories (`.ariadna_planning/phases/`) are NOT deleted — they accumulate across milestones as raw execution history. Phase numbering continues (v1.0 phases 1-4, v1.1 phases 5-8, etc.).
 
 After archival, the AI still handles:
 - Reorganizing ROADMAP.md with milestone grouping (requires judgment)
@@ -397,8 +397,8 @@ After `milestone complete` has archived, reorganize ROADMAP.md with milestone gr
 **Then delete originals:**
 
 ```bash
-rm .planning/ROADMAP.md
-rm .planning/REQUIREMENTS.md
+rm .ariadna_planning/ROADMAP.md
+rm .ariadna_planning/REQUIREMENTS.md
 ```
 
 </step>
@@ -412,7 +412,7 @@ Most STATE.md updates were handled by `milestone complete`, but verify and updat
 ```markdown
 ## Project Reference
 
-See: .planning/PROJECT.md (updated [today])
+See: .ariadna_planning/PROJECT.md (updated [today])
 
 **Core value:** [Current core value from PROJECT.md]
 **Current focus:** [Next milestone or "Planning next milestone"]
@@ -543,7 +543,7 @@ Key accomplishments:
 - [Item 2]
 - [Item 3]
 
-See .planning/MILESTONES.md for full details."
+See .ariadna_planning/MILESTONES.md for full details."
 ```
 
 Confirm: "Tagged: v[X.Y]"
@@ -562,7 +562,7 @@ git push origin v[X.Y]
 Commit milestone completion.
 
 ```bash
-ariadna-tools commit "chore: complete v[X.Y] milestone" --files .planning/milestones/v[X.Y]-ROADMAP.md .planning/milestones/v[X.Y]-REQUIREMENTS.md .planning/milestones/v[X.Y]-MILESTONE-AUDIT.md .planning/MILESTONES.md .planning/PROJECT.md .planning/STATE.md
+ariadna-tools commit "chore: complete v[X.Y] milestone" --files .ariadna_planning/milestones/v[X.Y]-ROADMAP.md .ariadna_planning/milestones/v[X.Y]-REQUIREMENTS.md .ariadna_planning/milestones/v[X.Y]-MILESTONE-AUDIT.md .ariadna_planning/MILESTONES.md .ariadna_planning/PROJECT.md .ariadna_planning/STATE.md
 ```
 ```
 
@@ -583,7 +583,7 @@ Archived:
 - milestones/v[X.Y]-ROADMAP.md
 - milestones/v[X.Y]-REQUIREMENTS.md
 
-Summary: .planning/MILESTONES.md
+Summary: .ariadna_planning/MILESTONES.md
 Tag: v[X.Y]
 
 ---

data/data/ariadna/workflows/diagnose-issues.md

@@ -7,9 +7,9 @@ Orchestrator stays lean: parse gaps, spawn agents, collect results, update UAT.
 </purpose>
 
 <paths>
-DEBUG_DIR=.planning/debug
+DEBUG_DIR=.ariadna_planning/debug
 
-Debug files use the `.planning/debug/` path (hidden directory with leading dot).
+Debug files use the `.ariadna_planning/debug/` path (hidden directory with leading dot).
 </paths>
 
 <core_principle>
@@ -151,14 +151,14 @@ For each gap in the Gaps section, add artifacts and missing fields:
   missing:
     - "Add after_commit callback to invalidate comment cache"
     - "Broadcast cache update via Turbo Stream"
-  debug_session: .planning/debug/comment-not-refreshing.md
+  debug_session: .ariadna_planning/debug/comment-not-refreshing.md
 ```
 
 Update status in frontmatter to "diagnosed".
 
 Commit the updated UAT.md:
 ```bash
-ariadna-tools commit "docs({phase}): add root causes from diagnosis" --files ".planning/phases/XX-name/{phase}-UAT.md"
+ariadna-tools commit "docs({phase}): add root causes from diagnosis" --files ".ariadna_planning/phases/XX-name/{phase}-UAT.md"
 ```
 </step>
 

data/data/ariadna/workflows/discovery-phase.md

@@ -116,7 +116,7 @@ For: Choosing between options, new external integration.
 
 7. Return to plan-phase.md.
 
-**Output:** `.planning/phases/XX-name/DISCOVERY.md`
+**Output:** `.ariadna_planning/phases/XX-name/DISCOVERY.md`
 </step>
 
 <step name="level_3_deep_dive">
@@ -169,7 +169,7 @@ For: Architectural decisions, novel problems, high-risk choices.
 
 8. Return to plan-phase.md.
 
-**Output:** `.planning/phases/XX-name/DISCOVERY.md` (comprehensive)
+**Output:** `.ariadna_planning/phases/XX-name/DISCOVERY.md` (comprehensive)
 </step>
 
 <step name="identify_unknowns">
@@ -203,7 +203,7 @@ Run the discovery:
 </step>
 
 <step name="create_discovery_output">
-Write `.planning/phases/XX-name/DISCOVERY.md`:
+Write `.ariadna_planning/phases/XX-name/DISCOVERY.md`:
 - Summary with recommendation
 - Key findings with sources
 - Code examples if applicable
@@ -246,7 +246,7 @@ If "address first": Gather user input on questions, update discovery.
 
 <step name="offer_next">
 ```
-Discovery complete: .planning/phases/XX-name/DISCOVERY.md
+Discovery complete: .ariadna_planning/phases/XX-name/DISCOVERY.md
 Recommendation: [one-liner]
 Confidence: [level]
 

data/data/ariadna/workflows/discuss-phase.md

@@ -284,7 +284,7 @@ Use values from init: `phase_dir`, `phase_slug`, `padded_phase`.
 
 If `phase_dir` is null (phase exists in roadmap but no directory):
 ```bash
-mkdir -p ".planning/phases/${padded_phase}-${phase_slug}"
+mkdir -p ".ariadna_planning/phases/${padded_phase}-${phase_slug}"
 ```
 
 **File location:** `${phase_dir}/${padded_phase}-CONTEXT.md`
@@ -350,7 +350,7 @@ Write file.
 Present summary and next steps:
 
 ```
-Created: .planning/phases/${PADDED_PHASE}-${SLUG}/${PADDED_PHASE}-CONTEXT.md
+Created: .ariadna_planning/phases/${PADDED_PHASE}-${SLUG}/${PADDED_PHASE}-CONTEXT.md
 
 ## Decisions Captured