ariadna 1.2.0 → 1.2.2

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

@@ -26,7 +26,7 @@ If `found` is false: Error and exit.
 ## Step 2: Check Existing Research
 
 ```bash
-ls .planning/phases/${PHASE}-*/RESEARCH.md 2>/dev/null
+ls .ariadna_planning/phases/${PHASE}-*/RESEARCH.md 2>/dev/null
 ```
 
 If exists: Offer update/view/skip options.
@@ -36,8 +36,8 @@ If exists: Offer update/view/skip options.
 ```bash
 # Phase section from roadmap (already loaded in PHASE_INFO)
 echo "$PHASE_INFO" | jq -r '.section'
-cat .planning/REQUIREMENTS.md 2>/dev/null
-cat .planning/phases/${PHASE}-*/*-CONTEXT.md 2>/dev/null
+cat .ariadna_planning/REQUIREMENTS.md 2>/dev/null
+cat .ariadna_planning/phases/${PHASE}-*/*-CONTEXT.md 2>/dev/null
 # Decisions from state-snapshot (structured JSON)
 ariadna-tools state-snapshot | jq '.decisions'
 ```
@@ -58,7 +58,7 @@ Phase context: {context_md}
 </context>
 
 <output>
-Write to: .planning/phases/${PHASE}-{slug}/${PHASE}-RESEARCH.md
+Write to: .ariadna_planning/phases/${PHASE}-{slug}/${PHASE}-RESEARCH.md
 </output>",
   subagent_type="ariadna-phase-researcher",
   model="{researcher_model}"

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

@@ -2,7 +2,7 @@
 Use this workflow when:
 - Starting a new session on an existing project
 - User says "continue", "what's next", "where were we", "resume"
-- Any planning operation when .planning/ already exists
+- Any planning operation when .ariadna_planning/ already exists
 - User returns after time away from project
 </trigger>
 
@@ -35,8 +35,8 @@ Parse JSON for: `state_exists`, `roadmap_exists`, `project_exists`, `planning_ex
 Read and parse STATE.md, then PROJECT.md:
 
 ```bash
-cat .planning/STATE.md
-cat .planning/PROJECT.md
+cat .ariadna_planning/STATE.md
+cat .ariadna_planning/PROJECT.md
 ```
 
 **From STATE.md extract:**
@@ -63,10 +63,10 @@ Look for incomplete work that needs attention:
 
 ```bash
 # Check for continue-here files (mid-plan resumption)
-ls .planning/phases/*/.continue-here*.md 2>/dev/null
+ls .ariadna_planning/phases/*/.continue-here*.md 2>/dev/null
 
 # Check for plans without summaries (incomplete execution)
-for plan in .planning/phases/*/*-PLAN.md; do
+for plan in .ariadna_planning/phases/*/*-PLAN.md; do
   summary="${plan/PLAN/SUMMARY}"
   [ ! -f "$summary" ] && echo "Incomplete: $plan"
 done 2>/dev/null
@@ -196,7 +196,7 @@ What would you like to do?
 **Note:** When offering phase planning, check for CONTEXT.md existence first:
 
 ```bash
-ls .planning/phases/XX-name/*-CONTEXT.md 2>/dev/null
+ls .ariadna_planning/phases/XX-name/*-CONTEXT.md 2>/dev/null
 ```
 
 If missing, suggest discuss-phase before plan. If exists, offer plan directly.
@@ -242,7 +242,7 @@ Based on user selection, route to appropriate workflow:
   ---
   ```
 - **Transition** → ./transition.md
-- **Check todos** → Read .planning/todos/pending/, present summary
+- **Check todos** → Read .ariadna_planning/todos/pending/, present summary
 - **Review alignment** → Read PROJECT.md, compare to current state
 - **Something else** → Ask what they need
 </step>
@@ -273,7 +273,7 @@ If STATE.md is missing but other artifacts exist:
 1. Read PROJECT.md → Extract "What This Is" and Core Value
 2. Read ROADMAP.md → Determine phases, find current position
 3. Scan \*-SUMMARY.md files → Extract decisions, concerns
-4. Count pending todos in .planning/todos/pending/
+4. Count pending todos in .ariadna_planning/todos/pending/
 5. Check for .continue-here files → Session continuity
 
 Reconstruct and write STATE.md, then proceed normally.
@@ -282,7 +282,7 @@ This handles cases where:
 
 - Project predates STATE.md introduction
 - File was accidentally deleted
-- Cloning repo without full .planning/ state
+- Cloning repo without full .ariadna_planning/ state
   </reconstruction>
 
 <quick_resume>

data/data/ariadna/workflows/set-profile.md

@@ -27,7 +27,7 @@ ariadna-tools config-ensure-section
 INIT=$(ariadna-tools state load)
 ```
 
-This creates `.planning/config.json` with defaults if missing and loads current config.
+This creates `.ariadna_planning/config.json` with defaults if missing and loads current config.
 </step>
 
 <step name="update_config">
@@ -40,7 +40,7 @@ Update `model_profile` field:
 }
 ```
 
-Write updated config back to `.planning/config.json`.
+Write updated config back to `.ariadna_planning/config.json`.
 </step>
 
 <step name="confirm">

data/data/ariadna/workflows/settings.md

@@ -1,5 +1,5 @@
 <purpose>
-Interactive configuration of Ariadna workflow agents (research, plan_check, verifier) and model profile selection via multi-question prompt. Updates .planning/config.json with user preferences.
+Interactive configuration of Ariadna workflow agents (research, plan_check, verifier) and model profile selection via multi-question prompt. Updates .ariadna_planning/config.json with user preferences.
 </purpose>
 
 <required_reading>
@@ -16,12 +16,12 @@ ariadna-tools config-ensure-section
 INIT=$(ariadna-tools state load)
 ```
 
-Creates `.planning/config.json` with defaults if missing and loads current config values.
+Creates `.ariadna_planning/config.json` with defaults if missing and loads current config values.
 </step>
 
 <step name="read_current">
 ```bash
-cat .planning/config.json
+cat .ariadna_planning/config.json
 ```
 
 Parse current values (default to `true` if not present):
@@ -106,7 +106,7 @@ Merge new settings into existing config.json:
 }
 ```
 
-Write updated config to `.planning/config.json`.
+Write updated config to `.ariadna_planning/config.json`.
 </step>
 
 <step name="confirm">

data/data/ariadna/workflows/transition.md

@@ -2,9 +2,9 @@
 
 **Read these files NOW:**
 
-1. `.planning/STATE.md`
-2. `.planning/PROJECT.md`
-3. `.planning/ROADMAP.md`
+1. `.ariadna_planning/STATE.md`
+2. `.ariadna_planning/PROJECT.md`
+3. `.ariadna_planning/ROADMAP.md`
 4. Current phase's plan files (`*-PLAN.md`)
 5. Current phase's summary files (`*-SUMMARY.md`)
 
@@ -25,8 +25,8 @@ Mark current phase complete and advance to next. This is the natural point where
 Before transition, read project state:
 
 ```bash
-cat .planning/STATE.md 2>/dev/null
-cat .planning/PROJECT.md 2>/dev/null
+cat .ariadna_planning/STATE.md 2>/dev/null
+cat .ariadna_planning/PROJECT.md 2>/dev/null
 ```
 
 Parse current position to verify we're transitioning the right phase.
@@ -39,8 +39,8 @@ Note accumulated context that may need updating after transition.
 Check current phase has all plan summaries:
 
 ```bash
-ls .planning/phases/XX-current/*-PLAN.md 2>/dev/null | sort
-ls .planning/phases/XX-current/*-SUMMARY.md 2>/dev/null | sort
+ls .ariadna_planning/phases/XX-current/*-PLAN.md 2>/dev/null | sort
+ls .ariadna_planning/phases/XX-current/*-SUMMARY.md 2>/dev/null | sort
 ```
 
 **Verification logic:**
@@ -53,7 +53,7 @@ ls .planning/phases/XX-current/*-SUMMARY.md 2>/dev/null | sort
 <config-check>
 
 ```bash
-cat .planning/config.json 2>/dev/null
+cat .ariadna_planning/config.json 2>/dev/null
 ```
 
 </config-check>
@@ -111,7 +111,7 @@ Wait for user decision.
 Check for lingering handoffs:
 
 ```bash
-ls .planning/phases/XX-current/.continue-here*.md 2>/dev/null
+ls .ariadna_planning/phases/XX-current/.continue-here*.md 2>/dev/null
 ```
 
 If found, delete them — phase is complete, handoffs are stale.
@@ -151,7 +151,7 @@ Evolve PROJECT.md to reflect learnings from completed phase.
 **Read phase summaries:**
 
 ```bash
-cat .planning/phases/XX-current/*-SUMMARY.md
+cat .ariadna_planning/phases/XX-current/*-SUMMARY.md
 ```
 
 **Assess requirement changes:**
@@ -259,7 +259,7 @@ Update Project Reference section in STATE.md.
 ```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 phase name]

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

@@ -36,7 +36,7 @@ Extract from init JSON: `phase_dir`, `phase_number`, `phase_name`, `has_plans`,
 Then load phase details and list plans/summaries:
 ```bash
 ariadna-tools roadmap get-phase "${phase_number}"
-grep -E "^| ${phase_number}" .planning/REQUIREMENTS.md 2>/dev/null
+grep -E "^| ${phase_number}" .ariadna_planning/REQUIREMENTS.md 2>/dev/null
 ls "$phase_dir"/*-SUMMARY.md "$phase_dir"/*-PLAN.md 2>/dev/null
 ```
 
@@ -143,7 +143,7 @@ Record status and evidence for each key link.
 <step name="verify_requirements">
 If REQUIREMENTS.md exists:
 ```bash
-grep -E "Phase ${PHASE_NUM}" .planning/REQUIREMENTS.md 2>/dev/null
+grep -E "Phase ${PHASE_NUM}" .ariadna_planning/REQUIREMENTS.md 2>/dev/null
 ```
 
 For each requirement: parse description → identify supporting truths/artifacts → status: ✓ SATISFIED / ✗ BLOCKED / ? NEEDS HUMAN.

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

@@ -34,7 +34,7 @@ Parse JSON for: `planner_model`, `checker_model`, `commit_docs`, `phase_found`,
 **First: Check for active UAT sessions**
 
 ```bash
-find .planning/phases -name "*-UAT.md" -type f 2>/dev/null | head -5
+find .ariadna_planning/phases -name "*-UAT.md" -type f 2>/dev/null | head -5
 ```
 
 **If active sessions exist AND no $ARGUMENTS provided:**
@@ -164,7 +164,7 @@ skipped: 0
 [none yet]
 ```
 
-Write to `.planning/phases/XX-name/{phase}-UAT.md`
+Write to `.ariadna_planning/phases/XX-name/{phase}-UAT.md`
 
 Proceed to `present_test`.
 </step>
@@ -292,7 +292,7 @@ Clear Current Test section:
 
 Commit the UAT file:
 ```bash
-ariadna-tools commit "test({phase}): complete UAT - {passed} passed, {issues} issues" --files ".planning/phases/XX-name/{phase}-UAT.md"
+ariadna-tools commit "test({phase}): complete UAT - {passed} passed, {issues} issues" --files ".ariadna_planning/phases/XX-name/{phase}-UAT.md"
 ```
 
 Present summary:
@@ -366,13 +366,13 @@ Task(
 **Mode:** gap_closure
 
 **UAT with diagnoses:**
-@.planning/phases/{phase_dir}/{phase}-UAT.md
+@.ariadna_planning/phases/{phase_dir}/{phase}-UAT.md
 
 **Project State:**
-@.planning/STATE.md
+@.ariadna_planning/STATE.md
 
 **Roadmap:**
-@.planning/ROADMAP.md
+@.ariadna_planning/ROADMAP.md
 
 </planning_context>
 
@@ -417,7 +417,7 @@ Task(
 **Phase Goal:** Close diagnosed gaps from UAT
 
 **Plans to verify:**
-@.planning/phases/{phase_dir}/*-PLAN.md
+@.ariadna_planning/phases/{phase_dir}/*-PLAN.md
 
 </verification_context>
 
@@ -456,7 +456,7 @@ Task(
 **Mode:** revision
 
 **Existing plans:**
-@.planning/phases/{phase_dir}/*-PLAN.md
+@.ariadna_planning/phases/{phase_dir}/*-PLAN.md
 
 **Checker issues:**
 {structured_issues_from_checker}

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

@@ -19,8 +19,8 @@ Routes to the add-phase workflow which handles:
 </objective>
 
 <execution_context>
-@.planning/ROADMAP.md
-@.planning/STATE.md
+@.ariadna_planning/ROADMAP.md
+@.ariadna_planning/STATE.md
 @~/.claude/ariadna/workflows/add-phase.md
 </execution_context>
 

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

@@ -23,7 +23,7 @@ Routes to the add-todo workflow which handles:
 </objective>
 
 <execution_context>
-@.planning/STATE.md
+@.ariadna_planning/STATE.md
 @~/.claude/ariadna/workflows/add-todo.md
 </execution_context>
 

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

@@ -24,16 +24,16 @@ Verify milestone achieved its definition of done. Check requirements coverage, c
 Version: $ARGUMENTS (optional — defaults to current milestone)
 
 **Original Intent:**
-@.planning/PROJECT.md
-@.planning/REQUIREMENTS.md
+@.ariadna_planning/PROJECT.md
+@.ariadna_planning/REQUIREMENTS.md
 
 **Planned Work:**
-@.planning/ROADMAP.md
-@.planning/config.json (if exists)
+@.ariadna_planning/ROADMAP.md
+@.ariadna_planning/config.json (if exists)
 
 **Completed Work:**
-Glob: .planning/phases/*/*-SUMMARY.md
-Glob: .planning/phases/*/*-VERIFICATION.md
+Glob: .ariadna_planning/phases/*/*-SUMMARY.md
+Glob: .ariadna_planning/phases/*/*-VERIFICATION.md
 </context>
 
 <process>

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

@@ -21,8 +21,8 @@ Routes to the check-todos workflow which handles:
 </objective>
 
 <execution_context>
-@.planning/STATE.md
-@.planning/ROADMAP.md
+@.ariadna_planning/STATE.md
+@.ariadna_planning/ROADMAP.md
 @~/.claude/ariadna/workflows/check-todos.md
 </execution_context>
 

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

@@ -25,10 +25,10 @@ Output: Milestone archived (roadmap + requirements), PROJECT.md evolved, git tag
 
 <context>
 **Project files:**
-- `.planning/ROADMAP.md`
-- `.planning/REQUIREMENTS.md`
-- `.planning/STATE.md`
-- `.planning/PROJECT.md`
+- `.ariadna_planning/ROADMAP.md`
+- `.ariadna_planning/REQUIREMENTS.md`
+- `.ariadna_planning/STATE.md`
+- `.ariadna_planning/PROJECT.md`
 
 **User input:**
 
@@ -41,7 +41,7 @@ Output: Milestone archived (roadmap + requirements), PROJECT.md evolved, git tag
 
 0. **Check for audit:**
 
-   - Look for `.planning/v{{version}}-MILESTONE-AUDIT.md`
+   - Look for `.ariadna_planning/v{{version}}-MILESTONE-AUDIT.md`
    - If missing or stale: recommend `/ariadna:audit-milestone` first
    - If audit status is `gaps_found`: recommend `/ariadna:plan-milestone-gaps` first
    - If audit status is `passed`: proceed to step 1
@@ -82,17 +82,17 @@ Output: Milestone archived (roadmap + requirements), PROJECT.md evolved, git tag
 
 4. **Archive milestone:**
 
-   - Create `.planning/milestones/v{{version}}-ROADMAP.md`
+   - Create `.ariadna_planning/milestones/v{{version}}-ROADMAP.md`
    - Extract full phase details from ROADMAP.md
    - Fill milestone-archive.md template
    - Update ROADMAP.md to one-line summary with link
 
 5. **Archive requirements:**
 
-   - Create `.planning/milestones/v{{version}}-REQUIREMENTS.md`
+   - Create `.ariadna_planning/milestones/v{{version}}-REQUIREMENTS.md`
    - Mark all v1 requirements as complete (checkboxes checked)
    - Note requirement outcomes (validated, adjusted, dropped)
-   - Delete `.planning/REQUIREMENTS.md` (fresh one created for next milestone)
+   - Delete `.ariadna_planning/REQUIREMENTS.md` (fresh one created for next milestone)
 
 6. **Update PROJECT.md:**
 
@@ -114,9 +114,9 @@ Output: Milestone archived (roadmap + requirements), PROJECT.md evolved, git tag
 
 <success_criteria>
 
-- Milestone archived to `.planning/milestones/v{{version}}-ROADMAP.md`
-- Requirements archived to `.planning/milestones/v{{version}}-REQUIREMENTS.md`
-- `.planning/REQUIREMENTS.md` deleted (fresh for next milestone)
+- Milestone archived to `.ariadna_planning/milestones/v{{version}}-ROADMAP.md`
+- Requirements archived to `.ariadna_planning/milestones/v{{version}}-REQUIREMENTS.md`
+- `.ariadna_planning/REQUIREMENTS.md` deleted (fresh for next milestone)
 - ROADMAP.md collapsed to one-line entry
 - PROJECT.md updated with current state
 - Git tag v{{version}} created

data/data/commands/ariadna/debug.md

@@ -22,7 +22,7 @@ User's issue: $ARGUMENTS
 
 Check for active sessions:
 ```bash
-ls .planning/debug/*.md 2>/dev/null | grep -v resolved | head -5
+ls .ariadna_planning/debug/*.md 2>/dev/null | grep -v resolved | head -5
 ```
 </context>
 
@@ -85,7 +85,7 @@ goal: find_and_fix
 </mode>
 
 <debug_file>
-Create: .planning/debug/{slug}.md
+Create: .ariadna_planning/debug/{slug}.md
 </debug_file>
 ```
 
@@ -129,7 +129,7 @@ Continue debugging {slug}. Evidence is in the debug file.
 </objective>
 
 <prior_state>
-Debug file: @.planning/debug/{slug}.md
+Debug file: @.ariadna_planning/debug/{slug}.md
 </prior_state>
 
 <checkpoint_response>

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

@@ -32,10 +32,10 @@ Extract implementation decisions that downstream agents need — researcher and
 Phase number: $ARGUMENTS (required)
 
 **Load project state:**
-@.planning/STATE.md
+@.ariadna_planning/STATE.md
 
 **Load roadmap:**
-@.planning/ROADMAP.md
+@.ariadna_planning/ROADMAP.md
 </context>
 
 <process>

data/data/commands/ariadna/execute-phase.md

@@ -1,7 +1,7 @@
 ---
 name: ariadna:execute-phase
 description: Execute all plans in a phase with wave-based parallelization
-argument-hint: "<phase-number> [--gaps-only] [--team]"
+argument-hint: "<phase-number> [--gaps-only] [--team] [--no-team]"
 allowed-tools:
   - Read
   - Write
@@ -26,7 +26,7 @@ Orchestrator stays lean: discover plans, analyze dependencies, group into waves,
 
 **Execution modes:**
 - **Wave mode (default):** Sequential waves of parallel `Task()` spawns. Standard for most phases.
-- **Team mode (`--team` flag or `team_execution: true` in config):** Creates a team with domain-specialized executor agents that coordinate via shared task list. Better for large phases with domain-split plans.
+- **Team mode (`--team` flag, `team_execution: true` or `"auto"` in config):** Creates a team with domain-specialized executor agents that coordinate via shared task list. Better for large phases with domain-split plans. When `team_execution: "auto"`, team mode activates for phases with 3+ plans across 2+ non-general domains.
 
 Context budget: ~15% orchestrator, 100% fresh per subagent.
 </objective>
@@ -42,14 +42,15 @@ Phase: $ARGUMENTS
 **Flags:**
 - `--gaps-only` — Execute only gap closure plans (plans with `gap_closure: true` in frontmatter). Use after verify-work creates fix plans.
 - `--team` — Use team-based execution with domain-specialized agents instead of wave-based execution.
+- `--no-team` — Force wave-based execution even when auto-detection would choose team mode.
 
-@.planning/ROADMAP.md
-@.planning/STATE.md
+@.ariadna_planning/ROADMAP.md
+@.ariadna_planning/STATE.md
 </context>
 
 <process>
 Execute the execute-phase workflow from @~/.claude/ariadna/workflows/execute-phase.md end-to-end.
 Preserve all workflow gates (wave/team execution, checkpoint handling, verification, state updates, routing).
 
-**Mode selection:** If `--team` flag is present or `team_execution: true` in config, use the `team_execution` step. Otherwise use the standard `execute_waves` step.
+**Mode selection:** Follow the `decide_execution_mode` step in the workflow to determine team vs wave execution based on flags, config, and plan analysis.
 </process>

data/data/commands/ariadna/insert-phase.md

@@ -23,8 +23,8 @@ Purpose: Handle urgent work discovered during execution without renumbering enti
 <context>
 Arguments: $ARGUMENTS (format: <after-phase-number> <description>)
 
-@.planning/ROADMAP.md
-@.planning/STATE.md
+@.ariadna_planning/ROADMAP.md
+@.ariadna_planning/STATE.md
 </context>
 
 <process>

data/data/commands/ariadna/list-phase-assumptions.md

@@ -24,10 +24,10 @@ Output: Conversational output only (no file creation) - ends with "What do you t
 Phase number: $ARGUMENTS (required)
 
 **Load project state first:**
-@.planning/STATE.md
+@.ariadna_planning/STATE.md
 
 **Load roadmap:**
-@.planning/ROADMAP.md
+@.ariadna_planning/ROADMAP.md
 </context>
 
 <process>

data/data/commands/ariadna/map-codebase.md

@@ -1,6 +1,6 @@
 ---
 name: ariadna:map-codebase
-description: Analyze codebase with parallel mapper agents to produce .planning/codebase/ documents
+description: Analyze codebase with parallel mapper agents to produce .ariadna_planning/codebase/ documents
 argument-hint: "[optional: specific area to map, e.g., 'api' or 'auth']"
 allowed-tools:
   - Read
@@ -14,9 +14,9 @@ allowed-tools:
 <objective>
 Analyze existing codebase using parallel ariadna-codebase-mapper agents to produce structured codebase documents.
 
-Each mapper agent explores a focus area and **writes documents directly** to `.planning/codebase/`. The orchestrator only receives confirmations, keeping context usage minimal.
+Each mapper agent explores a focus area and **writes documents directly** to `.ariadna_planning/codebase/`. The orchestrator only receives confirmations, keeping context usage minimal.
 
-Output: .planning/codebase/ folder with 7 structured documents about the codebase state.
+Output: .ariadna_planning/codebase/ folder with 7 structured documents about the codebase state.
 </objective>
 
 <execution_context>
@@ -27,7 +27,7 @@ Output: .planning/codebase/ folder with 7 structured documents about the codebas
 Focus area: $ARGUMENTS (optional - if provided, tells agents to focus on specific subsystem)
 
 **Load project state if exists:**
-Check for .planning/STATE.md - loads context if project already initialized
+Check for .ariadna_planning/STATE.md - loads context if project already initialized
 
 **This command can run:**
 - Before /ariadna:new-project (brownfield codebases) - creates codebase map first
@@ -49,8 +49,8 @@ Check for .planning/STATE.md - loads context if project already initialized
 </when_to_use>
 
 <process>
-1. Check if .planning/codebase/ already exists (offer to refresh or skip)
-2. Create .planning/codebase/ directory structure
+1. Check if .ariadna_planning/codebase/ already exists (offer to refresh or skip)
+2. Create .ariadna_planning/codebase/ directory structure
 3. Spawn 4 parallel ariadna-codebase-mapper agents:
    - Agent 1: tech focus → writes STACK.md, INTEGRATIONS.md
    - Agent 2: arch focus → writes ARCHITECTURE.md, STRUCTURE.md
@@ -63,7 +63,7 @@ Check for .planning/STATE.md - loads context if project already initialized
 </process>
 
 <success_criteria>
-- [ ] .planning/codebase/ directory created
+- [ ] .ariadna_planning/codebase/ directory created
 - [ ] All 7 codebase documents written by mapper agents
 - [ ] Documents follow template structure
 - [ ] Parallel agents completed without errors

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

@@ -15,11 +15,11 @@ Start a new milestone: questioning → research (optional) → requirements →
 Brownfield equivalent of new-project. Project exists, PROJECT.md has history. Gathers "what's next", updates PROJECT.md, then runs requirements → roadmap cycle.
 
 **Creates/Updates:**
-- `.planning/PROJECT.md` — updated with new milestone goals
-- `.planning/research/` — domain research (optional, NEW features only)
-- `.planning/REQUIREMENTS.md` — scoped requirements for this milestone
-- `.planning/ROADMAP.md` — phase structure (continues numbering)
-- `.planning/STATE.md` — reset for new milestone
+- `.ariadna_planning/PROJECT.md` — updated with new milestone goals
+- `.ariadna_planning/research/` — domain research (optional, NEW features only)
+- `.ariadna_planning/REQUIREMENTS.md` — scoped requirements for this milestone
+- `.ariadna_planning/ROADMAP.md` — phase structure (continues numbering)
+- `.ariadna_planning/STATE.md` — reset for new milestone
 
 **After:** `/ariadna:plan-phase [N]` to start execution.
 </objective>
@@ -36,13 +36,13 @@ Brownfield equivalent of new-project. Project exists, PROJECT.md has history. Ga
 Milestone name: $ARGUMENTS (optional - will prompt if not provided)
 
 **Load project context:**
-@.planning/PROJECT.md
-@.planning/STATE.md
-@.planning/MILESTONES.md
-@.planning/config.json
+@.ariadna_planning/PROJECT.md
+@.ariadna_planning/STATE.md
+@.ariadna_planning/MILESTONES.md
+@.ariadna_planning/config.json
 
 **Load milestone context (if exists, from /ariadna:discuss-milestone):**
-@.planning/MILESTONE-CONTEXT.md
+@.ariadna_planning/MILESTONE-CONTEXT.md
 </context>
 
 <process>

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

@@ -19,12 +19,12 @@ allowed-tools:
 Initialize a new project through streamlined flow: questioning → requirements → roadmap. Research skipped by default (Rails conventions pre-loaded); use --research for non-standard domains.
 
 **Creates:**
-- `.planning/PROJECT.md` — project context
-- `.planning/config.json` — workflow preferences (opinionated defaults)
-- `.planning/research/` — domain research (only with --research flag)
-- `.planning/REQUIREMENTS.md` — scoped requirements
-- `.planning/ROADMAP.md` — phase structure
-- `.planning/STATE.md` — project memory
+- `.ariadna_planning/PROJECT.md` — project context
+- `.ariadna_planning/config.json` — workflow preferences (opinionated defaults)
+- `.ariadna_planning/research/` — domain research (only with --research flag)
+- `.ariadna_planning/REQUIREMENTS.md` — scoped requirements
+- `.ariadna_planning/ROADMAP.md` — phase structure
+- `.ariadna_planning/STATE.md` — project memory
 
 **After this command:** Run `/ariadna:plan-phase 1` to start planning.
 </objective>

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

@@ -19,7 +19,7 @@ Routes to the pause-work workflow which handles:
 </objective>
 
 <execution_context>
-@.planning/STATE.md
+@.ariadna_planning/STATE.md
 @~/.claude/ariadna/workflows/pause-work.md
 </execution_context>
 

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

@@ -23,15 +23,15 @@ One command creates all fix phases — no manual `/ariadna:add-phase` per gap.
 
 <context>
 **Audit results:**
-Glob: .planning/v*-MILESTONE-AUDIT.md (use most recent)
+Glob: .ariadna_planning/v*-MILESTONE-AUDIT.md (use most recent)
 
 **Original intent (for prioritization):**
-@.planning/PROJECT.md
-@.planning/REQUIREMENTS.md
+@.ariadna_planning/PROJECT.md
+@.ariadna_planning/REQUIREMENTS.md
 
 **Current state:**
-@.planning/ROADMAP.md
-@.planning/STATE.md
+@.ariadna_planning/ROADMAP.md
+@.ariadna_planning/STATE.md
 </context>
 
 <process>