ariadna 1.3.0 → 2.0.0

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

@@ -1,40 +0,0 @@
----
-name: ariadna:plan-milestone-gaps
-description: Create phases to close all gaps identified by milestone audit
-allowed-tools:
-  - Read
-  - Write
-  - Bash
-  - Glob
-  - Grep
-  - AskUserQuestion
----
-<objective>
-Create all phases necessary to close gaps identified by `/ariadna:audit-milestone`.
-
-Reads MILESTONE-AUDIT.md, groups gaps into logical phases, creates phase entries in ROADMAP.md, and offers to plan each phase.
-
-One command creates all fix phases — no manual `/ariadna:add-phase` per gap.
-</objective>
-
-<execution_context>
-@~/.claude/ariadna/workflows/plan-milestone-gaps.md
-</execution_context>
-
-<context>
-**Audit results:**
-Glob: .ariadna_planning/v*-MILESTONE-AUDIT.md (use most recent)
-
-**Original intent (for prioritization):**
-@.ariadna_planning/PROJECT.md
-@.ariadna_planning/REQUIREMENTS.md
-
-**Current state:**
-@.ariadna_planning/ROADMAP.md
-@.ariadna_planning/STATE.md
-</context>
-
-<process>
-Execute the plan-milestone-gaps workflow from @~/.claude/ariadna/workflows/plan-milestone-gaps.md end-to-end.
-Preserve all workflow gates (audit loading, prioritization, phase grouping, user confirmation, roadmap updates).
-</process>

data/data/commands/ariadna/reapply-patches.md

@@ -1,110 +0,0 @@
----
-description: Reapply local modifications after an Ariadna update
-allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
----
-
-<purpose>
-After an Ariadna update wipes and reinstalls files, this command merges user's previously saved local modifications back into the new version. Uses intelligent comparison to handle cases where the upstream file also changed.
-</purpose>
-
-<process>
-
-## Step 1: Detect backed-up patches
-
-Check for local patches directory:
-
-```bash
-# Global install
-PATCHES_DIR="${HOME}/.claude/ariadna-local-patches"
-# Local install fallback
-if [ ! -d "$PATCHES_DIR" ]; then
-  PATCHES_DIR="./.claude/ariadna-local-patches"
-fi
-```
-
-Read `backup-meta.json` from the patches directory.
-
-**If no patches found:**
-```
-No local patches found. Nothing to reapply.
-
-Local patches are automatically saved when you run /ariadna:update
-after modifying any Ariadna workflow, command, or agent files.
-```
-Exit.
-
-## Step 2: Show patch summary
-
-```
-## Local Patches to Reapply
-
-**Backed up from:** v{from_version}
-**Current version:** {read VERSION file}
-**Files modified:** {count}
-
-| # | File | Status |
-|---|------|--------|
-| 1 | {file_path} | Pending |
-| 2 | {file_path} | Pending |
-```
-
-## Step 3: Merge each file
-
-For each file in `backup-meta.json`:
-
-1. **Read the backed-up version** (user's modified copy from `ariadna-local-patches/`)
-2. **Read the newly installed version** (current file after update)
-3. **Compare and merge:**
-
-   - If the new file is identical to the backed-up file: skip (modification was incorporated upstream)
-   - If the new file differs: identify the user's modifications and apply them to the new version
-
-   **Merge strategy:**
-   - Read both versions fully
-   - Identify sections the user added or modified (look for additions, not just differences from path replacement)
-   - Apply user's additions/modifications to the new version
-   - If a section the user modified was also changed upstream: flag as conflict, show both versions, ask user which to keep
-
-4. **Write merged result** to the installed location
-5. **Report status:**
-   - `Merged` — user modifications applied cleanly
-   - `Skipped` — modification already in upstream
-   - `Conflict` — user chose resolution
-
-## Step 4: Update manifest
-
-After reapplying, regenerate the file manifest so future updates correctly detect these as user modifications:
-
-```bash
-# The manifest will be regenerated on next /ariadna:update
-# For now, just note which files were modified
-```
-
-## Step 5: Cleanup option
-
-Ask user:
-- "Keep patch backups for reference?" → preserve `ariadna-local-patches/`
-- "Clean up patch backups?" → remove `ariadna-local-patches/` directory
-
-## Step 6: Report
-
-```
-## Patches Reapplied
-
-| # | File | Status |
-|---|------|--------|
-| 1 | {file_path} | ✓ Merged |
-| 2 | {file_path} | ○ Skipped (already upstream) |
-| 3 | {file_path} | ⚠ Conflict resolved |
-
-{count} file(s) updated. Your local modifications are active again.
-```
-
-</process>
-
-<success_criteria>
-- [ ] All backed-up patches processed
-- [ ] User modifications merged into new version
-- [ ] Conflicts resolved with user input
-- [ ] Status reported for each file
-</success_criteria>

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

@@ -1,187 +0,0 @@
----
-name: ariadna:research-phase
-description: Research how to implement a phase (standalone - usually use /ariadna:plan-phase instead)
-argument-hint: "[phase]"
-allowed-tools:
-  - Read
-  - Bash
-  - Task
----
-
-<objective>
-Research how to implement a phase. Spawns ariadna-phase-researcher agent with phase context.
-
-**Note:** This is a standalone research command. For most workflows, use `/ariadna:plan-phase` which integrates research automatically.
-
-**Use this command when:**
-- You want to research without planning yet
-- You want to re-research after planning is complete
-- You need to investigate before deciding if a phase is feasible
-
-**Orchestrator role:** Parse phase, validate against roadmap, check existing research, gather context, spawn researcher agent, present results.
-
-**Why subagent:** Research burns context fast (WebSearch, Context7 queries, source verification). Fresh 200k context for investigation. Main context stays lean for user interaction.
-</objective>
-
-<context>
-Phase number: $ARGUMENTS (required)
-
-Normalize phase input in step 1 before any directory lookups.
-</context>
-
-<process>
-
-## 0. Initialize Context
-
-```bash
-INIT=$(ariadna-tools init phase-op "$ARGUMENTS")
-```
-
-Extract from init JSON: `phase_dir`, `phase_number`, `phase_name`, `phase_found`, `commit_docs`, `has_research`.
-
-Resolve researcher model:
-```bash
-RESEARCHER_MODEL=$(ariadna-tools resolve-model ariadna-phase-researcher --raw)
-```
-
-## 1. Validate Phase
-
-```bash
-PHASE_INFO=$(ariadna-tools roadmap get-phase "${phase_number}")
-```
-
-**If `found` is false:** Error and exit. **If `found` is true:** Extract `phase_number`, `phase_name`, `goal` from JSON.
-
-## 2. Check Existing Research
-
-```bash
-ls .ariadna_planning/phases/${PHASE}-*/RESEARCH.md 2>/dev/null
-```
-
-**If exists:** Offer: 1) Update research, 2) View existing, 3) Skip. Wait for response.
-
-**If doesn't exist:** Continue.
-
-## 3. Gather Phase Context
-
-```bash
-# Phase section already loaded in PHASE_INFO
-echo "$PHASE_INFO" | jq -r '.section'
-cat .ariadna_planning/REQUIREMENTS.md 2>/dev/null
-cat .ariadna_planning/phases/${PHASE}-*/*-CONTEXT.md 2>/dev/null
-grep -A30 "### Decisions Made" .ariadna_planning/STATE.md 2>/dev/null
-```
-
-Present summary with phase description, requirements, prior decisions.
-
-## 4. Spawn ariadna-phase-researcher Agent
-
-Research modes: ecosystem (default), feasibility, implementation, comparison.
-
-```markdown
-<research_type>
-Phase Research — investigating HOW to implement a specific phase well.
-</research_type>
-
-<key_insight>
-The question is NOT "which library should I use?"
-
-The question is: "What do I not know that I don't know?"
-
-For this phase, discover:
-- What's the established architecture pattern?
-- What libraries form the standard stack?
-- What problems do people commonly hit?
-- What's SOTA vs what Claude's training thinks is SOTA?
-- What should NOT be hand-rolled?
-</key_insight>
-
-<objective>
-Research implementation approach for Phase {phase_number}: {phase_name}
-Mode: ecosystem
-</objective>
-
-<context>
-**Phase description:** {phase_description}
-**Requirements:** {requirements_list}
-**Prior decisions:** {decisions_if_any}
-**Phase context:** {context_md_content}
-</context>
-
-<downstream_consumer>
-Your RESEARCH.md will be loaded by `/ariadna:plan-phase` which uses specific sections:
-- `## Standard Stack` → Plans use these libraries
-- `## Architecture Patterns` → Task structure follows these
-- `## Don't Hand-Roll` → Tasks NEVER build custom solutions for listed problems
-- `## Common Pitfalls` → Verification steps check for these
-- `## Code Examples` → Task actions reference these patterns
-
-Be prescriptive, not exploratory. "Use X" not "Consider X or Y."
-</downstream_consumer>
-
-<quality_gate>
-Before declaring complete, verify:
-- [ ] All domains investigated (not just some)
-- [ ] Negative claims verified with official docs
-- [ ] Multiple sources for critical claims
-- [ ] Confidence levels assigned honestly
-- [ ] Section names match what plan-phase expects
-</quality_gate>
-
-<output>
-Write to: .ariadna_planning/phases/${PHASE}-{slug}/${PHASE}-RESEARCH.md
-</output>
-```
-
-```
-Task(
-  prompt="First, read ~/.claude/agents/ariadna-phase-researcher.md for your role and instructions.\n\n" + filled_prompt,
-  subagent_type="general-purpose",
-  model="{researcher_model}",
-  description="Research Phase {phase}"
-)
-```
-
-## 5. Handle Agent Return
-
-**`## RESEARCH COMPLETE`:** Display summary, offer: Plan phase, Dig deeper, Review full, Done.
-
-**`## CHECKPOINT REACHED`:** Present to user, get response, spawn continuation.
-
-**`## RESEARCH INCONCLUSIVE`:** Show what was attempted, offer: Add context, Try different mode, Manual.
-
-## 6. Spawn Continuation Agent
-
-```markdown
-<objective>
-Continue research for Phase {phase_number}: {phase_name}
-</objective>
-
-<prior_state>
-Research file: @.ariadna_planning/phases/${PHASE}-{slug}/${PHASE}-RESEARCH.md
-</prior_state>
-
-<checkpoint_response>
-**Type:** {checkpoint_type}
-**Response:** {user_response}
-</checkpoint_response>
-```
-
-```
-Task(
-  prompt="First, read ~/.claude/agents/ariadna-phase-researcher.md for your role and instructions.\n\n" + continuation_prompt,
-  subagent_type="general-purpose",
-  model="{researcher_model}",
-  description="Continue research Phase {phase}"
-)
-```
-
-</process>
-
-<success_criteria>
-- [ ] Phase validated against roadmap
-- [ ] Existing research checked
-- [ ] ariadna-phase-researcher spawned with context
-- [ ] Checkpoints handled correctly
-- [ ] User knows next steps
-</success_criteria>

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

@@ -1,40 +0,0 @@
----
-name: ariadna:resume-work
-description: Resume work from previous session with full context restoration
-allowed-tools:
-  - Read
-  - Bash
-  - Write
-  - AskUserQuestion
-  - SlashCommand
----
-
-<objective>
-Restore complete project context and resume work seamlessly from previous session.
-
-Routes to the resume-project workflow which handles:
-
-- STATE.md loading (or reconstruction if missing)
-- Checkpoint detection (.continue-here files)
-- Incomplete work detection (PLAN without SUMMARY)
-- Status presentation
-- Context-aware next action routing
-  </objective>
-
-<execution_context>
-@~/.claude/ariadna/workflows/resume-project.md
-</execution_context>
-
-<process>
-**Follow the resume-project workflow** from `@~/.claude/ariadna/workflows/resume-project.md`.
-
-The workflow handles all resumption logic including:
-
-1. Project existence verification
-2. STATE.md loading or reconstruction
-3. Checkpoint and incomplete work detection
-4. Visual status presentation
-5. Context-aware option offering (checks CONTEXT.md before suggesting plan vs discuss)
-6. Routing to appropriate next command
-7. Session continuity updates
-   </process>

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

@@ -1,34 +0,0 @@
----
-name: ariadna:set-profile
-description: Switch model profile for Ariadna agents (quality/balanced/budget)
-argument-hint: <profile>
-allowed-tools:
-  - Read
-  - Write
-  - Bash
----
-
-<objective>
-Switch the model profile used by Ariadna agents. Controls which Claude model each agent uses, balancing quality vs token spend.
-
-Routes to the set-profile workflow which handles:
-- Argument validation (quality/balanced/budget)
-- Config file creation if missing
-- Profile update in config.json
-- Confirmation with model table display
-</objective>
-
-<execution_context>
-@~/.claude/ariadna/workflows/set-profile.md
-</execution_context>
-
-<process>
-**Follow the set-profile workflow** from `@~/.claude/ariadna/workflows/set-profile.md`.
-
-The workflow handles all logic including:
-1. Profile argument validation
-2. Config file ensuring
-3. Config reading and updating
-4. Model table generation from MODEL_PROFILES
-5. Confirmation display
-</process>

data/data/commands/ariadna/settings.md

@@ -1,36 +0,0 @@
----
-name: ariadna:settings
-description: Configure Ariadna workflow toggles and model profile
-allowed-tools:
-  - Read
-  - Write
-  - Bash
-  - AskUserQuestion
----
-
-<objective>
-Interactive configuration of Ariadna workflow agents and model profile via multi-question prompt.
-
-Routes to the settings workflow which handles:
-- Config existence ensuring
-- Current settings reading and parsing
-- Interactive 5-question prompt (model, research, plan_check, verifier, branching)
-- Config merging and writing
-- Confirmation display with quick command references
-</objective>
-
-<execution_context>
-@~/.claude/ariadna/workflows/settings.md
-</execution_context>
-
-<process>
-**Follow the settings workflow** from `@~/.claude/ariadna/workflows/settings.md`.
-
-The workflow handles all logic including:
-1. Config file creation with defaults if missing
-2. Current config reading
-3. Interactive settings presentation with pre-selection
-4. Answer parsing and config merging
-5. File writing
-6. Confirmation display
-</process>

data/data/commands/ariadna/update.md

@@ -1,37 +0,0 @@
----
-name: ariadna:update
-description: Update Ariadna to latest version with changelog display
-allowed-tools:
-  - Bash
-  - AskUserQuestion
----
-
-<objective>
-Check for Ariadna updates, install if available, and display what changed.
-
-Routes to the update workflow which handles:
-- Version detection (local vs global installation)
-- gem version checking
-- Changelog fetching and display
-- User confirmation with clean install warning
-- Update execution and cache clearing
-- Restart reminder
-</objective>
-
-<execution_context>
-@~/.claude/ariadna/workflows/update.md
-</execution_context>
-
-<process>
-**Follow the update workflow** from `@~/.claude/ariadna/workflows/update.md`.
-
-The workflow handles all logic including:
-1. Installed version detection (local/global)
-2. Latest version checking via gem
-3. Version comparison
-4. Changelog fetching and extraction
-5. Clean install warning display
-6. User confirmation
-7. Update execution
-8. Cache clearing
-</process>