ariadna 1.2.0 → 1.2.2

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

@@ -71,7 +71,7 @@ Keep Accumulated Context section from previous milestone.
 Delete MILESTONE-CONTEXT.md if exists (consumed).
 
 ```bash
-ariadna-tools commit "docs: start milestone v[X.Y] [Name]" --files .planning/PROJECT.md .planning/STATE.md
+ariadna-tools commit "docs: start milestone v[X.Y] [Name]" --files .ariadna_planning/PROJECT.md .ariadna_planning/STATE.md
 ```
 
 ## 7. Load Context and Resolve Models
@@ -110,7 +110,7 @@ ariadna-tools config-set workflow.research false
 ```
 
 ```bash
-mkdir -p .planning/research
+mkdir -p .ariadna_planning/research
 ```
 
 Spawn 4 parallel ariadna-project-researcher agents. Each uses this template with dimension-specific fields:
@@ -135,7 +135,7 @@ Focus ONLY on what's needed for the NEW features.
 <quality_gate>{GATES}</quality_gate>
 
 <output>
-Write to: .planning/research/{FILE}
+Write to: .ariadna_planning/research/{FILE}
 Use template: ~/.claude/ariadna/templates/research-project/{FILE}
 </output>
 ", subagent_type="ariadna-project-researcher", model="{researcher_model}", description="{DIMENSION} research")
@@ -157,9 +157,9 @@ After all 4 complete, spawn synthesizer:
 Task(prompt="
 Synthesize research outputs into SUMMARY.md.
 
-Read: .planning/research/STACK.md, FEATURES.md, ARCHITECTURE.md, PITFALLS.md
+Read: .ariadna_planning/research/STACK.md, FEATURES.md, ARCHITECTURE.md, PITFALLS.md
 
-Write to: .planning/research/SUMMARY.md
+Write to: .ariadna_planning/research/SUMMARY.md
 Use template: ~/.claude/ariadna/templates/research-project/SUMMARY.md
 Commit after writing.
 ", subagent_type="ariadna-research-synthesizer", model="{synthesizer_model}", description="Synthesize research")
@@ -246,7 +246,7 @@ If "adjust": Return to scoping.
 
 **Commit requirements:**
 ```bash
-ariadna-tools commit "docs: define milestone v[X.Y] requirements" --files .planning/REQUIREMENTS.md
+ariadna-tools commit "docs: define milestone v[X.Y] requirements" --files .ariadna_planning/REQUIREMENTS.md
 ```
 
 ## 10. Create Roadmap
@@ -264,11 +264,11 @@ ariadna-tools commit "docs: define milestone v[X.Y] requirements" --files .plann
 ```
 Task(prompt="
 <planning_context>
-@.planning/PROJECT.md
-@.planning/REQUIREMENTS.md
-@.planning/research/SUMMARY.md (if exists)
-@.planning/config.json
-@.planning/MILESTONES.md
+@.ariadna_planning/PROJECT.md
+@.ariadna_planning/REQUIREMENTS.md
+@.ariadna_planning/research/SUMMARY.md (if exists)
+@.ariadna_planning/config.json
+@.ariadna_planning/MILESTONES.md
 </planning_context>
 
 <instructions>
@@ -321,7 +321,7 @@ Success criteria:
 
 **Commit roadmap** (after approval):
 ```bash
-ariadna-tools commit "docs: create milestone v[X.Y] roadmap ([N] phases)" --files .planning/ROADMAP.md .planning/STATE.md .planning/REQUIREMENTS.md
+ariadna-tools commit "docs: create milestone v[X.Y] roadmap ([N] phases)" --files .ariadna_planning/ROADMAP.md .ariadna_planning/STATE.md .ariadna_planning/REQUIREMENTS.md
 ```
 
 ## 11. Done
@@ -335,10 +335,10 @@ ariadna-tools commit "docs: create milestone v[X.Y] roadmap ([N] phases)" --file
 
 | Artifact       | Location                    |
 |----------------|-----------------------------|
-| Project        | `.planning/PROJECT.md`      |
-| Research       | `.planning/research/`       |
-| Requirements   | `.planning/REQUIREMENTS.md` |
-| Roadmap        | `.planning/ROADMAP.md`      |
+| Project        | `.ariadna_planning/PROJECT.md`      |
+| Research       | `.ariadna_planning/research/`       |
+| Requirements   | `.ariadna_planning/REQUIREMENTS.md` |
+| Roadmap        | `.ariadna_planning/ROADMAP.md`      |
 
 **[N] phases** | **[X] requirements** | Ready to build ✓
 

data/data/ariadna/workflows/new-project.md

@@ -133,7 +133,7 @@ Loop until "Create PROJECT.md" selected.
 
 **If auto mode:** Synthesize from provided document. No "Ready?" gate was shown — proceed directly to commit.
 
-Synthesize all context into `.planning/PROJECT.md` using the template from `templates/project.md`.
+Synthesize all context into `.ariadna_planning/PROJECT.md` using the template from `templates/project.md`.
 
 **For greenfield projects:**
 
@@ -164,7 +164,7 @@ All Active requirements are hypotheses until shipped and validated.
 
 Infer Validated requirements from existing code:
 
-1. Read `.planning/codebase/ARCHITECTURE.md` and `STACK.md`
+1. Read `.ariadna_planning/codebase/ARCHITECTURE.md` and `STACK.md`
 2. Identify what the codebase already does
 3. These become the initial Validated set
 
@@ -211,15 +211,15 @@ Do not compress. Capture everything gathered.
 **Commit PROJECT.md:**
 
 ```bash
-mkdir -p .planning
-ariadna-tools commit "docs: initialize project" --files .planning/PROJECT.md
+mkdir -p .ariadna_planning
+ariadna-tools commit "docs: initialize project" --files .ariadna_planning/PROJECT.md
 ```
 
 ## 5. Workflow Configuration
 
 **Use opinionated defaults. Only ask if user wants to customize.**
 
-Apply these defaults directly to `.planning/config.json`:
+Apply these defaults directly to `.ariadna_planning/config.json`:
 
 ```json
 {
@@ -253,12 +253,12 @@ questions: [
 ]
 ```
 
-Create `.planning/config.json` with the defaults above, applying the user's depth selection.
+Create `.ariadna_planning/config.json` with the defaults above, applying the user's depth selection.
 
 **Commit config.json:**
 
 ```bash
-ariadna-tools commit "chore: add project config" --files .planning/config.json
+ariadna-tools commit "chore: add project config" --files .ariadna_planning/config.json
 ```
 
 **Note:** Run `/ariadna:settings` anytime to update these preferences (research, model profile, parallelization, etc.).
@@ -293,7 +293,7 @@ Researching [domain] ecosystem...
 
 Create research directory:
 ```bash
-mkdir -p .planning/research
+mkdir -p .ariadna_planning/research
 ```
 
 **Determine milestone context:**
@@ -349,7 +349,7 @@ Your STACK.md feeds into roadmap creation. Be prescriptive:
 </quality_gate>
 
 <output>
-Write to: .planning/research/STACK.md
+Write to: .ariadna_planning/research/STACK.md
 Use template: ~/.claude/ariadna/templates/research-project/STACK.md
 </output>
 ", subagent_type="general-purpose", model="{researcher_model}", description="Stack research")
@@ -389,7 +389,7 @@ Your FEATURES.md feeds into requirements definition. Categorize clearly:
 </quality_gate>
 
 <output>
-Write to: .planning/research/FEATURES.md
+Write to: .ariadna_planning/research/FEATURES.md
 Use template: ~/.claude/ariadna/templates/research-project/FEATURES.md
 </output>
 ", subagent_type="general-purpose", model="{researcher_model}", description="Features research")
@@ -429,7 +429,7 @@ Your ARCHITECTURE.md informs phase structure in roadmap. Include:
 </quality_gate>
 
 <output>
-Write to: .planning/research/ARCHITECTURE.md
+Write to: .ariadna_planning/research/ARCHITECTURE.md
 Use template: ~/.claude/ariadna/templates/research-project/ARCHITECTURE.md
 </output>
 ", subagent_type="general-purpose", model="{researcher_model}", description="Architecture research")
@@ -469,7 +469,7 @@ Your PITFALLS.md prevents mistakes in roadmap/planning. For each pitfall:
 </quality_gate>
 
 <output>
-Write to: .planning/research/PITFALLS.md
+Write to: .ariadna_planning/research/PITFALLS.md
 Use template: ~/.claude/ariadna/templates/research-project/PITFALLS.md
 </output>
 ", subagent_type="general-purpose", model="{researcher_model}", description="Pitfalls research")
@@ -485,14 +485,14 @@ Synthesize research outputs into SUMMARY.md.
 
 <research_files>
 Read these files:
-- .planning/research/STACK.md
-- .planning/research/FEATURES.md
-- .planning/research/ARCHITECTURE.md
-- .planning/research/PITFALLS.md
+- .ariadna_planning/research/STACK.md
+- .ariadna_planning/research/FEATURES.md
+- .ariadna_planning/research/ARCHITECTURE.md
+- .ariadna_planning/research/PITFALLS.md
 </research_files>
 
 <output>
-Write to: .planning/research/SUMMARY.md
+Write to: .ariadna_planning/research/SUMMARY.md
 Use template: ~/.claude/ariadna/templates/research-project/SUMMARY.md
 Commit after writing.
 </output>
@@ -511,7 +511,7 @@ Display research complete banner and key findings:
 **Table Stakes:** [from SUMMARY.md]
 **Watch Out For:** [from SUMMARY.md]
 
-Files: `.planning/research/`
+Files: `.ariadna_planning/research/`
 ```
 
 **If research not requested:** Continue to Step 7.
@@ -610,7 +610,7 @@ Cross-check requirements against Core Value from PROJECT.md. If gaps detected, s
 
 **Generate REQUIREMENTS.md:**
 
-Create `.planning/REQUIREMENTS.md` with:
+Create `.ariadna_planning/REQUIREMENTS.md` with:
 - v1 Requirements grouped by category (checkboxes, REQ-IDs)
 - v2 Requirements (deferred)
 - Out of Scope (explicit exclusions with reasoning)
@@ -658,7 +658,7 @@ If "adjust": Return to scoping.
 **Commit requirements:**
 
 ```bash
-ariadna-tools commit "docs: define v1 requirements" --files .planning/REQUIREMENTS.md
+ariadna-tools commit "docs: define v1 requirements" --files .ariadna_planning/REQUIREMENTS.md
 ```
 
 ## 8. Create Roadmap
@@ -679,19 +679,19 @@ Task(prompt="
 <planning_context>
 
 **Project:**
-@.planning/PROJECT.md
+@.ariadna_planning/PROJECT.md
 
 **Requirements:**
-@.planning/REQUIREMENTS.md
+@.ariadna_planning/REQUIREMENTS.md
 
 **Research (if exists):**
-@.planning/research/SUMMARY.md
+@.ariadna_planning/research/SUMMARY.md
 
 **Rails Conventions (pre-loaded domain knowledge):**
 @~/.claude/ariadna/references/rails-conventions.md
 
 **Config:**
-@.planning/config.json
+@.ariadna_planning/config.json
 
 </planning_context>
 
@@ -780,7 +780,7 @@ Use AskUserQuestion:
   User feedback on roadmap:
   [user's notes]
 
-  Current ROADMAP.md: @.planning/ROADMAP.md
+  Current ROADMAP.md: @.ariadna_planning/ROADMAP.md
 
   Update the roadmap based on feedback. Edit files in place.
   Return ROADMAP REVISED with changes made.
@@ -790,12 +790,12 @@ Use AskUserQuestion:
 - Present revised roadmap
 - Loop until user approves
 
-**If "Review full file":** Display raw `cat .planning/ROADMAP.md`, then re-ask.
+**If "Review full file":** Display raw `cat .ariadna_planning/ROADMAP.md`, then re-ask.
 
 **Commit roadmap (after approval or auto mode):**
 
 ```bash
-ariadna-tools commit "docs: create roadmap ([N] phases)" --files .planning/ROADMAP.md .planning/STATE.md .planning/REQUIREMENTS.md
+ariadna-tools commit "docs: create roadmap ([N] phases)" --files .ariadna_planning/ROADMAP.md .ariadna_planning/STATE.md .ariadna_planning/REQUIREMENTS.md
 ```
 
 ## 9. Done
@@ -811,11 +811,11 @@ Present completion with next steps:
 
 | Artifact       | Location                    |
 |----------------|-----------------------------|
-| Project        | `.planning/PROJECT.md`      |
-| Config         | `.planning/config.json`     |
-| Research       | `.planning/research/`       |
-| Requirements   | `.planning/REQUIREMENTS.md` |
-| Roadmap        | `.planning/ROADMAP.md`      |
+| Project        | `.ariadna_planning/PROJECT.md`      |
+| Config         | `.ariadna_planning/config.json`     |
+| Research       | `.ariadna_planning/research/`       |
+| Requirements   | `.ariadna_planning/REQUIREMENTS.md` |
+| Roadmap        | `.ariadna_planning/ROADMAP.md`      |
 
 **[N] phases** | **[X] requirements** | Ready to build ✓
 
@@ -842,23 +842,23 @@ Present completion with next steps:
 
 <output>
 
-- `.planning/PROJECT.md`
-- `.planning/config.json`
-- `.planning/research/` (if research selected)
+- `.ariadna_planning/PROJECT.md`
+- `.ariadna_planning/config.json`
+- `.ariadna_planning/research/` (if research selected)
   - `STACK.md`
   - `FEATURES.md`
   - `ARCHITECTURE.md`
   - `PITFALLS.md`
   - `SUMMARY.md`
-- `.planning/REQUIREMENTS.md`
-- `.planning/ROADMAP.md`
-- `.planning/STATE.md`
+- `.ariadna_planning/REQUIREMENTS.md`
+- `.ariadna_planning/ROADMAP.md`
+- `.ariadna_planning/STATE.md`
 
 </output>
 
 <success_criteria>
 
-- [ ] .planning/ directory created
+- [ ] .ariadna_planning/ directory created
 - [ ] Git repo initialized
 - [ ] Brownfield detection completed
 - [ ] Deep questioning completed (threads followed, not rushed)

data/data/ariadna/workflows/pause-work.md

@@ -13,7 +13,7 @@ Find current phase directory from most recently modified files:
 
 ```bash
 # Find most recent phase directory with work
-ls -lt .planning/phases/*/PLAN.md 2>/dev/null | head -1 | grep -oP 'phases/\K[^/]+'
+ls -lt .ariadna_planning/phases/*/PLAN.md 2>/dev/null | head -1 | grep -oP 'phases/\K[^/]+'
 ```
 
 If no active phase detected, ask user which phase they're pausing work on.
@@ -34,7 +34,7 @@ Ask user for clarifications if needed via conversational questions.
 </step>
 
 <step name="write">
-**Write handoff to `.planning/phases/XX-name/.continue-here.md`:**
+**Write handoff to `.ariadna_planning/phases/XX-name/.continue-here.md`:**
 
 ```markdown
 ---
@@ -92,13 +92,13 @@ timestamp=$(ariadna-tools current-timestamp full --raw)
 
 <step name="commit">
 ```bash
-ariadna-tools commit "wip: [phase-name] paused at task [X]/[Y]" --files .planning/phases/*/.continue-here.md
+ariadna-tools commit "wip: [phase-name] paused at task [X]/[Y]" --files .ariadna_planning/phases/*/.continue-here.md
 ```
 </step>
 
 <step name="confirm">
 ```
-✓ Handoff created: .planning/phases/[XX-name]/.continue-here.md
+✓ Handoff created: .ariadna_planning/phases/[XX-name]/.continue-here.md
 
 Current state:
 

data/data/ariadna/workflows/plan-milestone-gaps.md

@@ -12,7 +12,7 @@ Read all files referenced by the invoking prompt's execution_context before star
 
 ```bash
 # Find the most recent audit file
-ls -t .planning/v*-MILESTONE-AUDIT.md 2>/dev/null | head -1
+ls -t .ariadna_planning/v*-MILESTONE-AUDIT.md 2>/dev/null | head -1
 ```
 
 Parse YAML frontmatter to extract structured gaps:
@@ -126,13 +126,13 @@ Add new phases to current milestone:
 ## 7. Create Phase Directories
 
 ```bash
-mkdir -p ".planning/phases/{NN}-{name}"
+mkdir -p ".ariadna_planning/phases/{NN}-{name}"
 ```
 
 ## 8. Commit Roadmap Update
 
 ```bash
-ariadna-tools commit "docs(roadmap): add gap closure phases {N}-{M}" --files .planning/ROADMAP.md
+ariadna-tools commit "docs(roadmap): add gap closure phases {N}-{M}" --files .ariadna_planning/ROADMAP.md
 ```
 
 ## 9. Offer Next Steps
@@ -157,7 +157,7 @@ ariadna-tools commit "docs(roadmap): add gap closure phases {N}-{M}" --files .pl
 
 **Also available:**
 - `/ariadna:execute-phase {N}` — if plans already exist
-- `cat .planning/ROADMAP.md` — see updated roadmap
+- `cat .ariadna_planning/ROADMAP.md` — see updated roadmap
 
 ---
 

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

@@ -27,13 +27,13 @@ Parse JSON for: `researcher_model`, `planner_model`, `checker_model`, `research_
 
 ## 2. Parse and Normalize Arguments
 
-Extract from $ARGUMENTS: phase number (integer or decimal like `2.1`), flags (`--research`, `--skip-research`, `--gaps`, `--skip-verify`, `--skip-context`).
+Extract from $ARGUMENTS: phase number (integer or decimal like `2.1`), flags (`--research`, `--skip-research`, `--gaps`, `--skip-verify`, `--skip-context`, `--skip-approval`).
 
 **If no phase number:** Detect next unplanned phase from roadmap.
 
 **If `phase_found` is false:** Validate phase exists in ROADMAP.md. If valid, create the directory using `phase_slug` and `padded_phase` from init:
 ```bash
-mkdir -p ".planning/phases/${padded_phase}-${phase_slug}"
+mkdir -p ".ariadna_planning/phases/${padded_phase}-${phase_slug}"
 ```
 
 **Existing artifacts from init:** `has_research`, `has_plans`, `plan_count`.
@@ -56,32 +56,30 @@ Use `context_content` from init JSON (already loaded via `--include context`).
 
 Analyze the phase goal from `roadmap_content` and determine if there are implementation decisions the user should weigh in on.
 
-**Quick assessment — does this phase need context?**
+**Categorize the phase — determines context behavior:**
 
-- Pure infrastructure / setup / configuration → No context needed, skip
-- Standard CRUD (models, controllers, views) → No context needed, skip
-- User-facing features with UI/UX decisions → Context helpful
-- Features with multiple valid approaches → Context helpful
+- **Category A** (infrastructure, setup, config, standard CRUD, testing, migrations, background jobs) → Skip context entirely. Display: `Context: Skipped (infrastructure/standard phase)`. Continue to step 5.
+- **Category B** (user-facing features, UI/UX decisions, user workflows, multiple valid approaches) → Show context question below.
 
-**If context would be helpful:** Offer inline clarification with a single AskUserQuestion:
+**Category B only — offer inline clarification.** Identify 2-3 specific gray areas from the phase goal (e.g., "unclear: how should password reset flow work?" or "multiple options: modal vs. inline form for editing"). Include them in the question text:
 
 ```
 questions: [
   {
     header: "Context",
-    question: "Phase {X}: {Name} has some implementation choices. Want to discuss them before planning?",
+    question: "Phase {X}: {Name} has gray areas:\n- {gray_area_1}\n- {gray_area_2}\n- {gray_area_3}\nWant to clarify before planning?",
     multiSelect: false,
     options: [
-      { label: "Plan directly (Recommended)", description: "Planner will make reasonable choices, you review the plan" },
-      { label: "Quick discussion", description: "Clarify 2-3 key decisions inline" },
+      { label: "Quick discussion (Recommended)", description: "Clarify these decisions inline — prevents plan mismatches" },
+      { label: "Plan directly", description: "Planner will make reasonable choices, you review the plan" },
       { label: "Full discussion", description: "Run /ariadna:discuss-phase for detailed context gathering" }
     ]
   }
 ]
 ```
 
-- **"Plan directly":** Continue to step 5. Planner will use its judgment for ambiguous areas.
 - **"Quick discussion":** Identify 2-3 key gray areas and ask focused AskUserQuestion for each. Write a lightweight CONTEXT.md to the phase directory. Then continue to step 5.
+- **"Plan directly":** Continue to step 5. Planner will use its judgment for ambiguous areas.
 - **"Full discussion":** Exit and tell user to run `/ariadna:discuss-phase {X}` first, then return.
 
 **CRITICAL:** Use `context_content` from INIT — pass to planner and checker agents.
@@ -251,7 +249,7 @@ Task(
 
 ## 9. Handle Planner Return
 
-- **`## PLANNING COMPLETE`:** Display plan count. If `--skip-verify` or `plan_checker_enabled` is false (from init): skip to step 13. Otherwise: step 10.
+- **`## PLANNING COMPLETE`:** Display plan count. If `--skip-verify` or `plan_checker_enabled` is false (from init): skip to step 13 (approval gate). Otherwise: step 10.
 - **`## CHECKPOINT REACHED`:** Present to user, get response, spawn continuation (step 12)
 - **`## PLANNING INCONCLUSIVE`:** Show attempts, offer: Add context / Retry / Manual
 
@@ -306,7 +304,7 @@ Task(
 
 ## 11. Handle Checker Return
 
-- **`## VERIFICATION PASSED`:** Display confirmation, proceed to step 13.
+- **`## VERIFICATION PASSED`:** Display confirmation, proceed to step 13 (approval gate).
 - **`## ISSUES FOUND`:** Classify issues and proceed to step 12.
 
 ## 12. Handle Checker Issues (Inline Fix, No Revision Loop)
@@ -351,7 +349,7 @@ questions: [
 ]
 ```
 
-- **"Accept as-is":** Proceed to step 13.
+- **"Accept as-is":** Proceed to step 13 (approval gate).
 - **"Re-plan":** Spawn planner in revision mode (single attempt, not a loop):
 
 ```
@@ -363,11 +361,36 @@ Task(
 )
 ```
 
-After planner returns, proceed to step 13 (no re-check loop).
+After planner returns, proceed to step 13 (approval gate, no re-check loop).
 
 - **"Fix manually":** Display file paths and exit.
 
-## 13. Present Final Status
+## 13. User Plan Approval Gate
+
+**Skip if:** `--skip-approval` flag, `--gaps` mode (gap closures already user-directed), or `requirements_content` is null (no REQUIREMENTS.md).
+
+**Otherwise:** Cross-reference each requirement mapped to this phase (from `requirements_content`) against the plans' `must_haves.truths` (from plan frontmatter). Present a single `AskUserQuestion`:
+
+```
+questions: [
+  {
+    header: "Plan Review",
+    question: "Phase {X}: {Name} — {N} plan(s) covering these requirements:\n\n| REQ-ID | Requirement | Covered By |\n|--------|-------------|------------|\n| {id} | {description} | Plan {plan_number}: {what_it_builds} |\n| {id} | {description} | ⚠ Not covered |\n\nApprove plans for execution?",
+    multiSelect: false,
+    options: [
+      { label: "Approve", description: "Plans look good, proceed to execution" },
+      { label: "Review details", description: "Show full plan files before deciding" },
+      { label: "Adjust", description: "Give feedback for a single re-plan attempt" }
+    ]
+  }
+]
+```
+
+- **"Approve":** Proceed to step 14.
+- **"Review details":** Display full content of each PLAN.md file in the phase directory. Then re-ask the same question (Approve / Adjust only).
+- **"Adjust":** Ask user for feedback with a follow-up AskUserQuestion (freeform). Spawn planner in revision mode with user feedback (single attempt, no loop). Then proceed to step 14.
+
+## 14. Present Final Status
 
 Route to `<offer_next>`.
 
@@ -404,14 +427,14 @@ Verification: {Passed | Passed with fixes | Skipped}
 ───────────────────────────────────────────────────────────────
 
 **Also available:**
-- cat .planning/phases/{phase-dir}/*-PLAN.md — review plans
+- cat .ariadna_planning/phases/{phase-dir}/*-PLAN.md — review plans
 - /ariadna:plan-phase {X} --research — re-research first
 
 ───────────────────────────────────────────────────────────────
 </offer_next>
 
 <success_criteria>
-- [ ] .planning/ directory validated
+- [ ] .ariadna_planning/ directory validated
 - [ ] Phase validated against roadmap
 - [ ] Phase directory created if needed
 - [ ] Context handled: existing CONTEXT.md used, inline gathering offered, or skipped
@@ -422,6 +445,7 @@ Verification: {Passed | Passed with fixes | Skipped}
 - [ ] ariadna-plan-checker spawned (unless --skip-verify)
 - [ ] Minor checker issues fixed inline by orchestrator (no revision loop)
 - [ ] Major checker issues presented to user for decision
+- [ ] User approved plans (or --skip-approval / --gaps flag used / no REQUIREMENTS.md)
 - [ ] User sees status between agent spawns
 - [ ] User knows next steps
 </success_criteria>

data/data/ariadna/workflows/progress.md

@@ -19,7 +19,7 @@ Extract from init JSON: `project_exists`, `roadmap_exists`, `state_exists`, `pha
 
 **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 `.planning/` directory):
+If `project_exists` is false (no `.ariadna_planning/` directory):
 
 ```
 No planning structure found.
@@ -85,7 +85,7 @@ Use this instead of manually reading/parsing ROADMAP.md.
 - 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 .planning/debug/*.md 2>/dev/null | grep -v resolved | wc -l`
+- Check for active debug sessions: `ls .ariadna_planning/debug/*.md 2>/dev/null | grep -v resolved | wc -l`
   </step>
 
 <step name="report">
@@ -141,9 +141,9 @@ CONTEXT: [✓ if has_context | - if not]
 List files in the current phase directory:
 
 ```bash
-ls -1 .planning/phases/[current-phase-dir]/*-PLAN.md 2>/dev/null | wc -l
-ls -1 .planning/phases/[current-phase-dir]/*-SUMMARY.md 2>/dev/null | wc -l
-ls -1 .planning/phases/[current-phase-dir]/*-UAT.md 2>/dev/null | wc -l
+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."
@@ -154,7 +154,7 @@ Check for UAT.md files with status "diagnosed" (has gaps needing fixes).
 
 ```bash
 # Check for diagnosed UAT with gaps
-grep -l "status: diagnosed" .planning/phases/[current-phase-dir]/*-UAT.md 2>/dev/null
+grep -l "status: diagnosed" .ariadna_planning/phases/[current-phase-dir]/*-UAT.md 2>/dev/null
 ```
 
 Track:

data/data/ariadna/workflows/quick.md

@@ -1,5 +1,5 @@
 <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 `.planning/quick/`, and updates STATE.md's "Quick Tasks Completed" table.
+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>
@@ -52,7 +52,7 @@ mkdir -p "${task_dir}"
 Create the directory for this quick task:
 
 ```bash
-QUICK_DIR=".planning/quick/${next_num}-${slug}"
+QUICK_DIR=".ariadna_planning/quick/${next_num}-${slug}"
 mkdir -p "$QUICK_DIR"
 ```
 
@@ -80,7 +80,7 @@ Task(
 **Description:** ${DESCRIPTION}
 
 **Project State:**
-@.planning/STATE.md
+@.ariadna_planning/STATE.md
 
 </planning_context>
 
@@ -121,7 +121,7 @@ Task(
 Execute quick task ${next_num}.
 
 Plan: @${QUICK_DIR}/${next_num}-PLAN.md
-Project state: @.planning/STATE.md
+Project state: @.ariadna_planning/STATE.md
 
 <constraints>
 - Execute all tasks in the plan
@@ -191,7 +191,7 @@ Use Edit tool to make these changes atomically
 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 .planning/STATE.md
+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:
@@ -222,7 +222,7 @@ Ready for next task: /ariadna:quick
 - [ ] User provides task description
 - [ ] Slug generated (lowercase, hyphens, max 40 chars)
 - [ ] Next number calculated (001, 002, 003...)
-- [ ] Directory created at `.planning/quick/NNN-slug/`
+- [ ] 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

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

@@ -65,7 +65,7 @@ Present removal summary and confirm:
 Removing Phase {target}: {Name}
 
 This will:
-- Delete: .planning/phases/{target}-{slug}/
+- Delete: .ariadna_planning/phases/{target}-{slug}/
 - Renumber all subsequent phases
 - Update: ROADMAP.md, STATE.md
 
@@ -102,7 +102,7 @@ Extract from result: `removed`, `directory_deleted`, `renamed_directories`, `ren
 Stage and commit the removal:
 
 ```bash
-ariadna-tools commit "chore: remove phase {target} ({original-phase-name})" --files .planning/
+ariadna-tools commit "chore: remove phase {target} ({original-phase-name})" --files .ariadna_planning/
 ```
 
 The commit message preserves the historical record of what was removed.
@@ -115,7 +115,7 @@ Present completion summary:
 Phase {target} ({original-name}) removed.
 
 Changes:
-- Deleted: .planning/phases/{target}-{slug}/
+- Deleted: .ariadna_planning/phases/{target}-{slug}/
 - Renumbered: {N} directories and {M} files
 - Updated: ROADMAP.md, STATE.md
 - Committed: chore: remove phase {target} ({original-name})