ariadna 1.3.1 → 2.0.0

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

@@ -1,327 +1,28 @@
-<purpose>
-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: .ariadna_planning/codebase/ folder with 7 structured documents about the codebase state.
-</purpose>
-
-<philosophy>
-**Why dedicated mapper agents:**
-- Fresh context per domain (no token contamination)
-- Agents write documents directly (no context transfer back to orchestrator)
-- Orchestrator only summarizes what was created (minimal context usage)
-- Faster execution (agents run simultaneously)
-
-**Document quality over length:**
-Include enough detail to be useful as reference. Prioritize practical examples (especially code patterns) over arbitrary brevity.
-
-**Always include file paths:**
-Documents are reference material for Claude when planning/executing. Always include actual file paths formatted with backticks: `app/services/user_service.rb`.
-</philosophy>
-
-<process>
-
-<step name="init_context" priority="first">
-Load codebase mapping context:
-
-```bash
-INIT=$(ariadna-tools init map-codebase)
-```
-
-Extract from init JSON: `mapper_model`, `commit_docs`, `codebase_dir`, `existing_maps`, `has_maps`, `codebase_dir_exists`.
-</step>
-
-<step name="check_existing">
-Check if .ariadna_planning/codebase/ already exists using `has_maps` from init context.
-
-If `codebase_dir_exists` is true:
-```bash
-ls -la .ariadna_planning/codebase/
-```
-
-**If exists:**
-
-```
-.ariadna_planning/codebase/ already exists with these documents:
-[List files found]
-
-What's next?
-1. Refresh - Delete existing and remap codebase
-2. Update - Keep existing, only update specific documents
-3. Skip - Use existing codebase map as-is
-```
-
-Wait for user response.
-
-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
-
-**If doesn't exist:**
-Continue to create_structure.
-</step>
-
-<step name="create_structure">
-Create .ariadna_planning/codebase/ directory:
-
-```bash
-mkdir -p .ariadna_planning/codebase
-```
-
-**Expected output files:**
-- STACK.md (from tech mapper)
-- INTEGRATIONS.md (from tech mapper)
-- ARCHITECTURE.md (from arch mapper)
-- STRUCTURE.md (from arch mapper)
-- CONVENTIONS.md (from quality mapper)
-- TESTING.md (from quality mapper)
-- CONCERNS.md (from concerns mapper)
-
-Continue to spawn_agents.
-</step>
-
-<step name="spawn_agents">
-Spawn 4 parallel ariadna-codebase-mapper agents.
-
-Use Task tool with `subagent_type="ariadna-codebase-mapper"`, `model="{mapper_model}"`, and `run_in_background=true` for parallel execution.
-
-**CRITICAL:** Use the dedicated `ariadna-codebase-mapper` agent, NOT `Explore`. The mapper agent writes documents directly.
-
-**Agent 1: Tech Focus**
-
-Task tool parameters:
-```
-subagent_type: "ariadna-codebase-mapper"
-model: "{mapper_model}"
-run_in_background: true
-description: "Map codebase tech stack"
-```
-
-Prompt:
-```
-Focus: tech
-
-Analyze this codebase for technology stack and external integrations.
-
-Write these documents to .ariadna_planning/codebase/:
-- STACK.md - Languages, runtime, frameworks, dependencies, configuration
-- INTEGRATIONS.md - External APIs, databases, auth providers, webhooks
-
-Explore thoroughly. Write documents directly using templates. Return confirmation only.
-```
-
-**Agent 2: Architecture Focus**
-
-Task tool parameters:
-```
-subagent_type: "ariadna-codebase-mapper"
-model: "{mapper_model}"
-run_in_background: true
-description: "Map codebase architecture"
-```
-
-Prompt:
-```
-Focus: arch
-
-Analyze this codebase architecture and directory structure.
-
-Write these documents to .ariadna_planning/codebase/:
-- ARCHITECTURE.md - Pattern, layers, data flow, abstractions, entry points
-- STRUCTURE.md - Directory layout, key locations, naming conventions
-
-Explore thoroughly. Write documents directly using templates. Return confirmation only.
-```
-
-**Agent 3: Quality Focus**
-
-Task tool parameters:
-```
-subagent_type: "ariadna-codebase-mapper"
-model: "{mapper_model}"
-run_in_background: true
-description: "Map codebase conventions"
-```
-
-Prompt:
-```
-Focus: quality
-
-Analyze this codebase for coding conventions and testing patterns.
-
-Write these documents to .ariadna_planning/codebase/:
-- CONVENTIONS.md - Code style, naming, patterns, error handling
-- TESTING.md - Framework, structure, mocking, coverage
-
-Explore thoroughly. Write documents directly using templates. Return confirmation only.
-```
-
-**Agent 4: Concerns Focus**
-
-Task tool parameters:
-```
-subagent_type: "ariadna-codebase-mapper"
-model: "{mapper_model}"
-run_in_background: true
-description: "Map codebase concerns"
-```
-
-Prompt:
-```
-Focus: concerns
-
-Analyze this codebase for technical debt, known issues, and areas of concern.
-
-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.
-```
-
-Continue to collect_confirmations.
-</step>
-
-<step name="collect_confirmations">
-Wait for all 4 agents to complete.
-
-Read each agent's output file to collect confirmations.
-
-**Expected confirmation format from each agent:**
-```
-## Mapping Complete
-
-**Focus:** {focus}
-**Documents written:**
-- `.ariadna_planning/codebase/{DOC1}.md` ({N} lines)
-- `.ariadna_planning/codebase/{DOC2}.md` ({N} lines)
-
-Ready for orchestrator summary.
-```
-
-**What you receive:** Just file paths and line counts. NOT document contents.
-
-If any agent failed, note the failure and continue with successful documents.
-
-Continue to verify_output.
-</step>
-
-<step name="verify_output">
-Verify all documents created successfully:
-
-```bash
-ls -la .ariadna_planning/codebase/
-wc -l .ariadna_planning/codebase/*.md
-```
-
-**Verification checklist:**
-- All 7 documents exist
-- No empty documents (each should have >20 lines)
-
-If any documents missing or empty, note which agents may have failed.
-
-Continue to scan_for_secrets.
-</step>
-
-<step name="scan_for_secrets">
-**CRITICAL SECURITY CHECK:** Scan output files for accidentally leaked secrets before committing.
-
-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_-]+\.)' .ariadna_planning/codebase/*.md 2>/dev/null && SECRETS_FOUND=true || SECRETS_FOUND=false
-```
-
-**If SECRETS_FOUND=true:**
-
-```
-⚠️  SECURITY ALERT: Potential secrets detected in codebase documents!
-
-Found patterns that look like API keys or tokens in:
-[show grep output]
-
-This would expose credentials if committed.
-
-**Action required:**
-1. Review the flagged content above
-2. If these are real secrets, they must be removed before committing
-3. Consider adding sensitive files to Claude Code "Deny" permissions
-
-Pausing before commit. Reply "safe to proceed" if the flagged content is not actually sensitive, or edit the files first.
-```
-
-Wait for user confirmation before continuing to commit_codebase_map.
-
-**If SECRETS_FOUND=false:**
-
-Continue to commit_codebase_map.
-</step>
-
-<step name="commit_codebase_map">
-Commit the codebase map:
-
-```bash
-ariadna-tools commit "docs: map existing codebase" --files .ariadna_planning/codebase/*.md
-```
-
-Continue to offer_next.
-</step>
-
-<step name="offer_next">
-Present completion summary and next steps.
-
-**Get line counts:**
-```bash
-wc -l .ariadna_planning/codebase/*.md
-```
-
-**Output format:**
-
-```
-Codebase mapping complete.
-
-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
-- CONVENTIONS.md ([N] lines) - Code style and patterns
-- TESTING.md ([N] lines) - Test structure and practices
-- INTEGRATIONS.md ([N] lines) - External services and APIs
-- CONCERNS.md ([N] lines) - Technical debt and issues
-
-
 ---
-
-## ▶ Next Up
-
-**Initialize project** — use codebase context for planning
-
-`/ariadna:new-project`
-
-<sub>`/clear` first → fresh context window</sub>
-
+name: map-codebase
+description: Analyze an existing codebase with 4 parallel mapper agents and produce 7 structured documents in .ariadna_planning/codebase/.
 ---
 
-**Also available:**
-- Re-run mapping: `/ariadna:map-codebase`
-- Review specific file: `cat .ariadna_planning/codebase/STACK.md`
-- Edit any document before proceeding
+## Goal
+Produce a complete, reference-quality snapshot of the codebase — stack, architecture, conventions, and concerns — by running 4 specialized mapper agents in parallel. Each agent writes its documents directly; the orchestrator only collects confirmations and line counts.
 
----
+## Context Loading
+```bash
+INIT=$(ariadna-tools init map-codebase)
 ```
+Parse: `mapper_model`, `codebase_dir_exists`, `existing_maps`. If `codebase_dir_exists` is true, offer: Refresh (delete + remap), Update (remap specific documents), or Skip (use existing). Create `.ariadna_planning/codebase/` if it doesn't exist.
 
-End workflow.
-</step>
+## Constraints
+- Spawn all 4 agents in a single message with `run_in_background=true` (true parallel execution)
+- Agents are `ariadna-codebase-mapper` — NOT general-purpose; they write documents directly and return only confirmation + line counts
+- Required outputs: STACK.md, INTEGRATIONS.md (agent 1 — tech), ARCHITECTURE.md, STRUCTURE.md (agent 2 — arch), CONVENTIONS.md, TESTING.md (agent 3 — quality), CONCERNS.md (agent 4 — concerns)
+- Run secret scan (`grep -E` for API key patterns) on all output files before committing; pause for user confirmation if secrets detected
+- Documents must include actual file paths formatted in backticks — they are reference material for planners
 
-</process>
+## Success Criteria
+- All 7 documents exist in `.ariadna_planning/codebase/` with >20 lines each
+- Secret scan passes (no credentials leaked)
+- Committed with `docs: map existing codebase`
 
-<success_criteria>
-- .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
-- All 7 codebase documents exist
-- Clear completion summary with line counts
-- User offered clear next steps in Ariadna style
-</success_criteria>
+## On Completion
+Display document list with line counts. Offer `/ariadna:new-project` as the natural next step with a `/clear` reminder.