ariadna 1.2.1 → 1.2.2

data/data/ariadna/workflows/help.md

@@ -38,7 +38,7 @@ One command takes you from idea to ready-for-planning:
 - Requirements definition with v1/v2/out-of-scope scoping
 - Roadmap creation with phase breakdown and success criteria
 
-Creates all `.planning/` artifacts:
+Creates all `.ariadna_planning/` artifacts:
 - `PROJECT.md` — vision and requirements
 - `config.json` — workflow mode (interactive/yolo)
 - `research/` — domain research (if selected)
@@ -52,7 +52,7 @@ Usage: `/ariadna:new-project`
 Map an existing codebase for brownfield projects.
 
 - Analyzes codebase with parallel Explore agents
-- Creates `.planning/codebase/` with 7 focused documents
+- Creates `.ariadna_planning/codebase/` with 7 focused documents
 - Covers stack, architecture, structure, conventions, testing, integrations, concerns
 - Use before `/ariadna:new-project` on existing codebases
 
@@ -91,13 +91,13 @@ Usage: `/ariadna:list-phase-assumptions 3`
 **`/ariadna:plan-phase <number>`**
 Create detailed execution plan for a specific phase.
 
-- Generates `.planning/phases/XX-phase-name/XX-YY-PLAN.md`
+- Generates `.ariadna_planning/phases/XX-phase-name/XX-YY-PLAN.md`
 - Breaks phase into concrete, actionable tasks
 - Includes verification criteria and success measures
 - Multiple plans per phase supported (XX-01, XX-02, etc.)
 
 Usage: `/ariadna:plan-phase 1`
-Result: Creates `.planning/phases/01-foundation/01-01-PLAN.md`
+Result: Creates `.ariadna_planning/phases/01-foundation/01-01-PLAN.md`
 
 ### Execution
 
@@ -118,13 +118,13 @@ Execute small, ad-hoc tasks with Ariadna guarantees but skip optional agents.
 
 Quick mode uses the same system with a shorter path:
 - Spawns planner + executor (skips researcher, checker, verifier)
-- Quick tasks live in `.planning/quick/` separate from planned phases
+- Quick tasks live in `.ariadna_planning/quick/` separate from planned phases
 - Updates STATE.md tracking (not ROADMAP.md)
 
 Use when you know exactly what to do and the task is small enough to not need research or verification.
 
 Usage: `/ariadna:quick`
-Result: Creates `.planning/quick/NNN-slug/PLAN.md`, `.planning/quick/NNN-slug/SUMMARY.md`
+Result: Creates `.ariadna_planning/quick/NNN-slug/PLAN.md`, `.ariadna_planning/quick/NNN-slug/SUMMARY.md`
 
 ### Roadmap Management
 
@@ -222,10 +222,10 @@ Usage: `/ariadna:pause-work`
 Systematic debugging with persistent state across context resets.
 
 - Gathers symptoms through adaptive questioning
-- Creates `.planning/debug/[slug].md` to track investigation
+- Creates `.ariadna_planning/debug/[slug].md` to track investigation
 - Investigates using scientific method (evidence → hypothesis → test)
 - Survives `/clear` — run `/ariadna:debug` with no args to resume
-- Archives resolved issues to `.planning/debug/resolved/`
+- Archives resolved issues to `.ariadna_planning/debug/resolved/`
 
 Usage: `/ariadna:debug "login button doesn't work"`
 Usage: `/ariadna:debug` (resume active session)
@@ -236,7 +236,7 @@ Usage: `/ariadna:debug` (resume active session)
 Capture idea or task as todo from current conversation.
 
 - Extracts context from conversation (or uses provided description)
-- Creates structured todo file in `.planning/todos/pending/`
+- Creates structured todo file in `.ariadna_planning/todos/pending/`
 - Infers area from file paths for grouping
 - Checks for duplicates before creating
 - Updates STATE.md todo count
@@ -297,7 +297,7 @@ Configure workflow toggles and model profile interactively.
 
 - Toggle researcher, plan checker, verifier agents
 - Select model profile (quality/balanced/budget)
-- Updates `.planning/config.json`
+- Updates `.ariadna_planning/config.json`
 
 Usage: `/ariadna:settings`
 
@@ -337,7 +337,7 @@ Usage: `/ariadna:join-discord`
 ## Files & Structure
 
 ```
-.planning/
+.ariadna_planning/
 ├── PROJECT.md            # Project vision
 ├── ROADMAP.md            # Current phase breakdown
 ├── STATE.md              # Project memory & context
@@ -380,24 +380,24 @@ Set during `/ariadna:new-project`:
 - Executes plans without confirmation
 - Only stops for critical checkpoints
 
-Change anytime by editing `.planning/config.json`
+Change anytime by editing `.ariadna_planning/config.json`
 
 ## Planning Configuration
 
-Configure how planning artifacts are managed in `.planning/config.json`:
+Configure how planning artifacts are managed in `.ariadna_planning/config.json`:
 
 **`planning.commit_docs`** (default: `true`)
 - `true`: Planning artifacts committed to git (standard workflow)
 - `false`: Planning artifacts kept local-only, not committed
 
 When `commit_docs: false`:
-- Add `.planning/` to your `.gitignore`
+- Add `.ariadna_planning/` to your `.gitignore`
 - Useful for OSS contributions, client projects, or keeping planning private
 - All planning files still work normally, just not tracked in git
 
 **`planning.search_gitignored`** (default: `false`)
 - `true`: Add `--no-ignore` to broad ripgrep searches
-- Only needed when `.planning/` is gitignored and you want project-wide searches to include it
+- Only needed when `.ariadna_planning/` is gitignored and you want project-wide searches to include it
 
 Example config:
 ```json
@@ -463,8 +463,8 @@ Example config:
 
 ## Getting Help
 
-- Read `.planning/PROJECT.md` for project vision
-- Read `.planning/STATE.md` for current context
-- Check `.planning/ROADMAP.md` for phase status
+- Read `.ariadna_planning/PROJECT.md` for project vision
+- Read `.ariadna_planning/STATE.md` for current context
+- Check `.ariadna_planning/ROADMAP.md` for phase status
 - Run `/ariadna:progress` to check where you're up to
 </reference>

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

@@ -39,7 +39,7 @@ INIT=$(ariadna-tools init phase-op "${after_phase}")
 
 Check `roadmap_exists` from init JSON. If false:
 ```
-ERROR: No roadmap found (.planning/ROADMAP.md)
+ERROR: No roadmap found (.ariadna_planning/ROADMAP.md)
 ```
 Exit.
 </step>
@@ -55,7 +55,7 @@ The CLI handles:
 - Verifying target phase exists in ROADMAP.md
 - Calculating next decimal phase number (checking existing decimals on disk)
 - Generating slug from description
-- Creating the phase directory (`.planning/phases/{N.M}-{slug}/`)
+- Creating the phase directory (`.ariadna_planning/phases/{N.M}-{slug}/`)
 - Inserting the phase entry into ROADMAP.md after the target phase with (INSERTED) marker
 
 Extract from result: `phase_number`, `after_phase`, `name`, `slug`, `directory`.
@@ -64,7 +64,7 @@ Extract from result: `phase_number`, `after_phase`, `name`, `slug`, `directory`.
 <step name="update_project_state">
 Update STATE.md to reflect the inserted phase:
 
-1. Read `.planning/STATE.md`
+1. Read `.ariadna_planning/STATE.md`
 2. Under "## Accumulated Context" → "### Roadmap Evolution" add entry:
    ```
    - Phase {decimal_phase} inserted after Phase {after_phase}: {description} (URGENT)
@@ -79,12 +79,12 @@ Present completion summary:
 ```
 Phase {decimal_phase} inserted after Phase {after_phase}:
 - Description: {description}
-- Directory: .planning/phases/{decimal-phase}-{slug}/
+- Directory: .ariadna_planning/phases/{decimal-phase}-{slug}/
 - Status: Not planned yet
 - Marker: (INSERTED) - indicates urgent work
 
-Roadmap updated: .planning/ROADMAP.md
-Project state updated: .planning/STATE.md
+Roadmap updated: .ariadna_planning/ROADMAP.md
+Project state updated: .ariadna_planning/STATE.md
 
 ---
 

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

@@ -24,7 +24,7 @@ Exit workflow.
 Validate phase exists in roadmap:
 
 ```bash
-cat .planning/ROADMAP.md | grep -i "Phase ${PHASE}"
+cat .ariadna_planning/ROADMAP.md | grep -i "Phase ${PHASE}"
 ```
 
 **If phase not found:**

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

@@ -1,9 +1,9 @@
 <purpose>
-Orchestrate parallel codebase mapper agents to analyze codebase and produce structured documents in .planning/codebase/
+Orchestrate parallel codebase mapper agents to analyze codebase and produce structured documents in .ariadna_planning/codebase/
 
 Each agent has fresh context, explores a specific focus area, and **writes documents directly**. The orchestrator only receives confirmation + line counts, then writes a summary.
 
-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.
 </purpose>
 
 <philosophy>
@@ -33,17 +33,17 @@ Extract from init JSON: `mapper_model`, `commit_docs`, `codebase_dir`, `existing
 </step>
 
 <step name="check_existing">
-Check if .planning/codebase/ already exists using `has_maps` from init context.
+Check if .ariadna_planning/codebase/ already exists using `has_maps` from init context.
 
 If `codebase_dir_exists` is true:
 ```bash
-ls -la .planning/codebase/
+ls -la .ariadna_planning/codebase/
 ```
 
 **If exists:**
 
 ```
-.planning/codebase/ already exists with these documents:
+.ariadna_planning/codebase/ already exists with these documents:
 [List files found]
 
 What's next?
@@ -54,7 +54,7 @@ What's next?
 
 Wait for user response.
 
-If "Refresh": Delete .planning/codebase/, continue to create_structure
+If "Refresh": Delete .ariadna_planning/codebase/, continue to create_structure
 If "Update": Ask which documents to update, continue to spawn_agents (filtered)
 If "Skip": Exit workflow
 
@@ -63,10 +63,10 @@ Continue to create_structure.
 </step>
 
 <step name="create_structure">
-Create .planning/codebase/ directory:
+Create .ariadna_planning/codebase/ directory:
 
 ```bash
-mkdir -p .planning/codebase
+mkdir -p .ariadna_planning/codebase
 ```
 
 **Expected output files:**
@@ -104,7 +104,7 @@ Focus: tech
 
 Analyze this codebase for technology stack and external integrations.
 
-Write these documents to .planning/codebase/:
+Write these documents to .ariadna_planning/codebase/:
 - STACK.md - Languages, runtime, frameworks, dependencies, configuration
 - INTEGRATIONS.md - External APIs, databases, auth providers, webhooks
 
@@ -127,7 +127,7 @@ Focus: arch
 
 Analyze this codebase architecture and directory structure.
 
-Write these documents to .planning/codebase/:
+Write these documents to .ariadna_planning/codebase/:
 - ARCHITECTURE.md - Pattern, layers, data flow, abstractions, entry points
 - STRUCTURE.md - Directory layout, key locations, naming conventions
 
@@ -150,7 +150,7 @@ Focus: quality
 
 Analyze this codebase for coding conventions and testing patterns.
 
-Write these documents to .planning/codebase/:
+Write these documents to .ariadna_planning/codebase/:
 - CONVENTIONS.md - Code style, naming, patterns, error handling
 - TESTING.md - Framework, structure, mocking, coverage
 
@@ -173,7 +173,7 @@ Focus: concerns
 
 Analyze this codebase for technical debt, known issues, and areas of concern.
 
-Write this document to .planning/codebase/:
+Write this document to .ariadna_planning/codebase/:
 - CONCERNS.md - Tech debt, bugs, security, performance, fragile areas
 
 Explore thoroughly. Write document directly using template. Return confirmation only.
@@ -193,8 +193,8 @@ Read each agent's output file to collect confirmations.
 
 **Focus:** {focus}
 **Documents written:**
-- `.planning/codebase/{DOC1}.md` ({N} lines)
-- `.planning/codebase/{DOC2}.md` ({N} lines)
+- `.ariadna_planning/codebase/{DOC1}.md` ({N} lines)
+- `.ariadna_planning/codebase/{DOC2}.md` ({N} lines)
 
 Ready for orchestrator summary.
 ```
@@ -210,8 +210,8 @@ Continue to verify_output.
 Verify all documents created successfully:
 
 ```bash
-ls -la .planning/codebase/
-wc -l .planning/codebase/*.md
+ls -la .ariadna_planning/codebase/
+wc -l .ariadna_planning/codebase/*.md
 ```
 
 **Verification checklist:**
@@ -230,7 +230,7 @@ Run secret pattern detection:
 
 ```bash
 # Check for common API key patterns in generated docs
-grep -E '(sk-[a-zA-Z0-9]{20,}|sk_live_[a-zA-Z0-9]+|sk_test_[a-zA-Z0-9]+|ghp_[a-zA-Z0-9]{36}|gho_[a-zA-Z0-9]{36}|glpat-[a-zA-Z0-9_-]+|AKIA[A-Z0-9]{16}|xox[baprs]-[a-zA-Z0-9-]+|-----BEGIN.*PRIVATE KEY|eyJ[a-zA-Z0-9_-]+\.eyJ[a-zA-Z0-9_-]+\.)' .planning/codebase/*.md 2>/dev/null && SECRETS_FOUND=true || SECRETS_FOUND=false
+grep -E '(sk-[a-zA-Z0-9]{20,}|sk_live_[a-zA-Z0-9]+|sk_test_[a-zA-Z0-9]+|ghp_[a-zA-Z0-9]{36}|gho_[a-zA-Z0-9]{36}|glpat-[a-zA-Z0-9_-]+|AKIA[A-Z0-9]{16}|xox[baprs]-[a-zA-Z0-9-]+|-----BEGIN.*PRIVATE KEY|eyJ[a-zA-Z0-9_-]+\.eyJ[a-zA-Z0-9_-]+\.)' .ariadna_planning/codebase/*.md 2>/dev/null && SECRETS_FOUND=true || SECRETS_FOUND=false
 ```
 
 **If SECRETS_FOUND=true:**
@@ -262,7 +262,7 @@ Continue to commit_codebase_map.
 Commit the codebase map:
 
 ```bash
-ariadna-tools commit "docs: map existing codebase" --files .planning/codebase/*.md
+ariadna-tools commit "docs: map existing codebase" --files .ariadna_planning/codebase/*.md
 ```
 
 Continue to offer_next.
@@ -273,7 +273,7 @@ Present completion summary and next steps.
 
 **Get line counts:**
 ```bash
-wc -l .planning/codebase/*.md
+wc -l .ariadna_planning/codebase/*.md
 ```
 
 **Output format:**
@@ -281,7 +281,7 @@ wc -l .planning/codebase/*.md
 ```
 Codebase mapping complete.
 
-Created .planning/codebase/:
+Created .ariadna_planning/codebase/:
 - STACK.md ([N] lines) - Technologies and dependencies
 - ARCHITECTURE.md ([N] lines) - System design and patterns
 - STRUCTURE.md ([N] lines) - Directory layout and organization
@@ -305,7 +305,7 @@ Created .planning/codebase/:
 
 **Also available:**
 - Re-run mapping: `/ariadna:map-codebase`
-- Review specific file: `cat .planning/codebase/STACK.md`
+- Review specific file: `cat .ariadna_planning/codebase/STACK.md`
 - Edit any document before proceeding
 
 ---
@@ -317,7 +317,7 @@ End workflow.
 </process>
 
 <success_criteria>
-- .planning/codebase/ directory created
+- .ariadna_planning/codebase/ directory created
 - 4 parallel ariadna-codebase-mapper agents spawned with run_in_background=true
 - Agents write documents directly (orchestrator doesn't receive document contents)
 - Read agent output files to collect confirmations

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)