maestro-flow 0.3.7 → 0.3.9

package/.claude/commands/maestro-verify.md

@@ -1,87 +1,106 @@
----
-name: maestro-verify
-description: Goal-Backward verification with 3-layer must-have checks, anti-pattern scan, Nyquist test coverage validation, and gap-fix plan generation
-argument-hint: "<phase> [--skip-tests] [--skip-antipattern]"
-allowed-tools:
-  - Read
-  - Write
-  - Edit
-  - Bash
-  - Glob
-  - Grep
-  - Agent
-  - AskUserQuestion
----
-<purpose>
-Verify phase execution results through three complementary methods:
-1. **Goal-Backward verification** — 3-layer check (Truths → Artifacts → Wiring) that validates goals are actually achieved, not just tasks completed
-2. **Anti-pattern scan** — detect stubs, placeholders, TODO/FIXME, empty returns in modified files
-3. **Nyquist test coverage validation** — requirement-to-test mapping with gap classification (COVERED/PARTIAL/MISSING)
-
-Core principle: **Task completion ≠ Goal achievement**. A task "create chat component" can be marked complete when the component is a placeholder. This verifier checks that the goal "working chat interface" is actually achieved.
-
-Produces verification.json with must-have checks, gaps, anti-patterns, and fix plans. Optionally produces validation.json with test coverage analysis.
-</purpose>
-
-<required_reading>
-@~/.maestro/workflows/verify.md
-</required_reading>
-
-<deferred_reading>
-- [verification.json](~/.maestro/templates/verification.json) — read when generating verification output
-- [validation.json](~/.maestro/templates/validation.json) — read when generating validation output
-- [index.json](~/.maestro/templates/index.json) — read when updating phase index
-</deferred_reading>
-
-<context>
-Phase: $ARGUMENTS (required -- phase number or slug)
-
-**Flags:**
-- `--skip-tests` -- Skip Nyquist test coverage validation (V2), only run Goal-Backward verification
-- `--skip-antipattern` -- Skip anti-pattern scan
-
-Context files resolved from `.workflow/phases/{NN}-{slug}/`:
-- index.json (phase metadata, success_criteria, plan, execution results)
-- plan.json (task overview)
-- .task/TASK-{NNN}.json (task definitions with convergence.criteria)
-- .summaries/TASK-{NNN}-summary.md (execution results)
-</context>
-
-<execution>
-Follow '~/.maestro/workflows/verify.md' completely.
-
-**Next-step routing on completion:**
-- All checks pass, no gaps → Skill({ skill: "quality-review", args: "{phase}" })
-- Gaps found (must-have failures or anti-pattern blockers) → Skill({ skill: "maestro-plan", args: "{phase} --gaps" })
-- Low test coverage (Nyquist gaps) → Skill({ skill: "quality-test-gen", args: "{phase}" })
-
-**Gap-fix closure loop:**
-Gaps found → maestro-plan --gaps → maestro-execute → maestro-verify (re-run)
-</execution>
-
-<error_codes>
-| Code | Severity | Condition | Recovery |
-|------|----------|-----------|----------|
-| E001 | error | Phase argument required | Check arguments format, re-run with correct input |
-| E002 | error | Phase directory not found | Check arguments format, re-run with correct input |
-| E003 | error | No execution results found (missing summaries) | Check arguments format, re-run with correct input |
-| W001 | warning | Test coverage below configured threshold | Review coverage gaps, run quality-test-gen |
-| W002 | warning | Anti-pattern blockers found in modified files | Fix anti-pattern blockers before proceeding |
-| W003 | warning | Wiki health below threshold (score < 80) | Review broken links and orphan specs |
-| W004 | warning | Wiki health check unavailable | Skipped — wiki may not be initialized |
-</error_codes>
-
-<success_criteria>
-- [ ] Must-haves established (from success_criteria, convergence.criteria, or derived)
-- [ ] All truths verified with status and evidence (Layer 1)
-- [ ] All artifacts checked at L1 (exists), L2 (substantive), L3 (wired) (Layer 2)
-- [ ] Wiki health score reported (Layer 2.5) — warnings emitted if score < 80 or orphan specs found
-- [ ] All key links verified with evidence (Layer 3)
-- [ ] Anti-patterns scanned and categorized (unless skipped)
-- [ ] Nyquist test coverage assessed with gap classification (unless skipped)
-- [ ] Fix plans generated for identified gaps
-- [ ] Human verification items identified
-- [ ] verification.json written with complete results
-- [ ] validation.json written if test audit ran
-- [ ] index.json updated with verification status and timestamps
-</success_criteria>
+---
+name: maestro-verify
+description: Goal-Backward verification with 3-layer must-have checks, anti-pattern scan, Nyquist test coverage validation, and gap-fix plan generation
+argument-hint: "[phase] [--skip-tests] [--skip-antipattern] [--dir <path>]"
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Bash
+  - Glob
+  - Grep
+  - Agent
+  - AskUserQuestion
+---
+<purpose>
+Verify execution results through three complementary methods:
+1. **Goal-Backward verification** — 3-layer check (Truths → Artifacts → Wiring) that validates goals are actually achieved
+2. **Anti-pattern scan** — detect stubs, placeholders, TODO/FIXME, empty returns in modified files
+3. **Nyquist test coverage validation** — requirement-to-test mapping with gap classification
+
+Supports dual-level verification:
+- **Single plan**: `verify --dir scratch/plan-xxx` — verifies one plan, writes `verification.json` into plan dir
+- **Milestone**: `verify` (no args) — aggregates all execute artifacts for current milestone into `scratch/verify-{milestone}-{date}/milestone-verification.json`
+
+Registers VRF artifact in state.json on completion.
+</purpose>
+
+<required_reading>
+@~/.maestro/workflows/verify.md
+</required_reading>
+
+<deferred_reading>
+- [verification.json](~/.maestro/templates/verification.json) — read when generating output
+- [validation.json](~/.maestro/templates/validation.json) — read when generating test output
+</deferred_reading>
+
+<context>
+$ARGUMENTS — phase number or no args for milestone-wide, with optional flags.
+
+**Flags:**
+- `--skip-tests` -- Skip Nyquist test coverage validation, only run Goal-Backward
+- `--skip-antipattern` -- Skip anti-pattern scan
+- `--dir <path>` -- Verify specific plan directory
+
+**Scope routing:**
+
+| Invocation | Behavior |
+|-----------|----------|
+| `verify` (no args) | Milestone-level: verify all executed plans, aggregate results |
+| `verify 1` | Phase-level: verify all executed plans for phase 1 |
+| `verify --dir scratch/plan-xxx` | Single plan: verify specific plan directory |
+
+**Single plan output**: `verification.json` appended to plan's scratch dir
+**Milestone output**: `scratch/verify-{milestone-slug}-{date}/milestone-verification.json`
+
+**Artifact registration**: On completion, register VRF artifact:
+```jsonc
+{
+  "id": "VRF-{NNN}",
+  "type": "verify",
+  "milestone": "{current_milestone or null}",
+  "phase": null,
+  "scope": "milestone",
+  "path": "scratch/verify-{milestone-slug}-{date}",
+  "status": "completed",
+  "depends_on": ["EXC-001", "EXC-002", ...],
+  "harvested": false,
+  "created_at": "...",
+  "completed_at": "..."
+}
+```
+</context>
+
+<execution>
+Follow '~/.maestro/workflows/verify.md' completely.
+
+**Next-step routing on completion:**
+- All checks pass, no gaps → /quality-review
+- Gaps found (must-have failures or anti-pattern blockers) → /maestro-plan --gaps
+- Low test coverage (Nyquist gaps) → /quality-test-gen
+
+**Gap-fix closure loop:**
+Gaps found → maestro-plan --gaps → maestro-execute → maestro-verify (re-run)
+</execution>
+
+<error_codes>
+| Code | Severity | Condition | Recovery |
+|------|----------|-----------|----------|
+| E001 | error | No executed plans found for verification | Run maestro-execute first |
+| E002 | error | Plan directory not found | Check --dir path |
+| E003 | error | No execution results found (missing summaries) | Run maestro-execute first |
+| W001 | warning | Test coverage below configured threshold | Review coverage gaps |
+| W002 | warning | Anti-pattern blockers found in modified files | Fix blockers before proceeding |
+</error_codes>
+
+<success_criteria>
+- [ ] Must-haves established (from convergence.criteria in tasks)
+- [ ] All truths verified with status and evidence (Layer 1)
+- [ ] All artifacts checked at L1 (exists), L2 (substantive), L3 (wired) (Layer 2)
+- [ ] All key links verified with evidence (Layer 3)
+- [ ] Anti-patterns scanned and categorized (unless skipped)
+- [ ] Nyquist test coverage assessed (unless skipped)
+- [ ] Fix plans generated for identified gaps
+- [ ] verification.json written to plan dir (single plan) or milestone verify dir
+- [ ] VRF artifact registered in state.json
+</success_criteria>

package/.claude/commands/maestro.md

@@ -39,9 +39,9 @@ $ARGUMENTS — user intent text, or special keywords.
 - `--chain <name>` — Force a specific chain (bypass intent detection). Valid: full-lifecycle, spec-driven, brainstorm-driven, execute-verify, quality-loop, milestone-close, quick, review
 
 **State files read:**
-- `.workflow/state.json` — project state machine
+- `.workflow/state.json` — project state machine + artifact registry
 - `.workflow/roadmap.md` — milestone/phase structure
-- `.workflow/phases/*/index.json` — per-phase metadata and progress
+- `.workflow/scratch/*/plan.json` — plan metadata (via artifact registry paths)
 </context>
 
 <execution>
@@ -65,7 +65,7 @@ When `-y` is active, maestro propagates auto flags to downstream commands. Only
 | quality-test-gen | *(none)* | No auto flag — generates tests normally |
 | quality-debug | *(none)* | No auto flag — runs diagnosis normally |
 | quality-retrospective | `--auto-yes` | Accept all routing recommendations (spec/note/issue) without prompting |
-| maestro-phase-transition | *(none)* | No auto flag — validates and transitions |
+| maestro-milestone-audit | *(none)* | No auto flag — validates milestone readiness |
 | manage-learn | *(none)* | No auto flag — pure file operation, no prompts |
 
 Commands not listed (manage-*, spec-*, milestone-*) have no auto flags and execute as-is.
@@ -75,6 +75,12 @@ In auto mode, maestro also:
 - Skips chain confirmation (Step 5d)
 - Auto-skips on step errors (retry once, then skip and continue)
 
+**Context cleanup hint:**
+
+After completing step 3+, proactively suggest `-c` resume:
+- Interactive mode: display `⚡ 已执行 {N} 步，上下文较重。可随时 /maestro -c 在新上下文中恢复。`
+- `-y` mode and step 4+: log one-line warning to status.json, continue.
+
 **Context window reminder:**
 
 Before each Step 7 Skill() call, if context usage is near the window limit:
@@ -87,7 +93,7 @@ Before each Step 7 Skill() call, if context usage is near the window limit:
 === MAESTRO SESSION COMPLETE ===
 Session: {session_id}
 Chain:   {chain_name} ({steps_completed}/{steps_total} steps)
-Phase:   {current_phase} (if applicable)
+Milestone: {current_milestone} (if applicable)
 Mode:    {auto | interactive}
 
 Steps:

package/.claude/commands/manage-codebase-rebuild.md

@@ -16,7 +16,7 @@ allowed-tools:
 <purpose>
 Perform a full rebuild of the .workflow/codebase/ documentation system from scratch. Scans the entire project source to identify components, features, requirements, and ADRs, then spawns parallel workflow-codebase-mapper agents to generate all documentation artifacts. This is a destructive operation that overwrites existing codebase docs.
 
-Can run before or after Skill({ skill: "maestro-init" }) -- works on any codebase with source files. Also serves the previous `spec-map` use case via `--focus <area>` for scoped dimension analysis.
+Can run before or after `/maestro-init` -- works on any codebase with source files. Also serves the previous `spec-map` use case via `--focus <area>` for scoped dimension analysis.
 </purpose>
 
 <required_reading>
@@ -51,8 +51,8 @@ Follow '~/.maestro/workflows/codebase-rebuild.md' completely.
 **When `--focus <area>` is set:** pass the area string to each mapper agent as scoping context; only regenerate the docs relevant to that scope (leave others untouched unless missing).
 
 **Next-step routing on completion:**
-- View updated project state → Skill({ skill: "manage-status" })
-- Incremental updates later → Skill({ skill: "manage-codebase-refresh" })
+- View updated project state → `/manage-status`
+- Incremental updates later → `/manage-codebase-refresh`
 </execution>
 
 <error_codes>
@@ -72,5 +72,5 @@ Follow '~/.maestro/workflows/codebase-rebuild.md' completely.
 - [ ] state.json updated with rebuild timestamp
 - [ ] project-tech.json refreshed with detected tech stack
 - [ ] project.md Tech Stack section updated if changes detected
-- [ ] Next step routing: Skill({ skill: "manage-status" }) or Skill({ skill: "manage-codebase-refresh" }) for incremental updates later
+- [ ] Next step routing: `/manage-status` or `/manage-codebase-refresh` for incremental updates later
 </success_criteria>

package/.claude/commands/manage-codebase-refresh.md

@@ -53,5 +53,5 @@ Follow '~/.maestro/workflows/codebase-refresh.md' completely.
 - [ ] Only affected docs refreshed (selective mapper re-run)
 - [ ] doc-index.json timestamps updated per affected entry
 - [ ] state.json updated with codebase_last_refreshed timestamp
-- [ ] Next step routing: Skill({ skill: "manage-status" }) or Skill({ skill: "spec-load" }) to use updated docs
+- [ ] Next step routing: `/manage-status` or `/spec-load` to use updated docs
 </success_criteria>

package/.claude/commands/manage-harvest.md

@@ -89,16 +89,16 @@ Follow '~/.maestro/workflows/harvest.md' Stages 1–8 in order. Key invariants:
 
 **Next-step routing on completion:**
 - Review wiki entries → `maestro wiki list --type note`
-- Connect wiki graph → `Skill({ skill: "wiki-connect", args: "--fix" })`
-- Triage issues → `Skill({ skill: "manage-issue", args: "list --source harvest" })`
-- View specs → `Skill({ skill: "spec-load", args: "--category general" })`
-- Full retrospective → `Skill({ skill: "quality-retrospective" })`
+- Connect wiki graph → `/wiki-connect --fix`
+- Triage issues → `/manage-issue list --source harvest`
+- View specs → `/spec-load --category general`
+- Full retrospective → `/quality-retrospective`
 </execution>
 
 <error_codes>
 | Code | Severity | Condition | Recovery |
 |------|----------|-----------|----------|
-| E001 | error | `.workflow/` not initialized | Run `Skill({ skill: "maestro-init" })` first |
+| E001 | error | `.workflow/` not initialized | Run `/maestro-init` first |
 | E002 | error | Invalid `--to` target (must be: wiki, spec, issue, auto) | Display valid options |
 | E003 | error | Invalid `--source` type | Display valid source types from registry |
 | E004 | error | Session ID not found in any source path | Show available sessions with `--source all` |

package/.claude/commands/manage-issue-discover.md

@@ -73,5 +73,5 @@ Follow '~/.maestro/workflows/issue-discover.md' completely.
 - [ ] Findings deduplicated before issue creation
 - [ ] Issues appended to issues.jsonl with correct schema
 - [ ] Discovery session fully traceable via session directory
-- [ ] Next step routing: Skill({ skill: "manage-issue-analyze", args: "<ISS-ID>" }) for root cause analysis, or Skill({ skill: "manage-issue", args: "list" }) to review all issues
+- [ ] Next step routing: `/manage-issue-analyze <ISS-ID>` for root cause analysis, or `/manage-issue list` to review all issues
 </success_criteria>

package/.claude/commands/manage-issue-execute.md

@@ -48,9 +48,9 @@ $ARGUMENTS -- ISS-ID (required) + optional flags.
 Follow '~/.maestro/workflows/issue-execute.md' completely.
 
 **Next-step routing on completion:**
-- Execution succeeded → Skill({ skill: "manage-issue", args: "close <ISS-ID> --resolution fixed" })
-- Execution failed → Skill({ skill: "quality-debug", args: "<failure description>" }) then retry
-- Want verification → Skill({ skill: "maestro-verify", args: "{phase}" })
+- Execution succeeded → `/manage-issue close <ISS-ID> --resolution fixed`
+- Execution failed → `/quality-debug <failure description>` then retry
+- Want verification → `/maestro-verify {phase}`
 </execution>
 
 <error_codes>
@@ -67,7 +67,7 @@ Follow '~/.maestro/workflows/issue-execute.md' completely.
 - [ ] Solution executed (or dry-run displayed)
 - [ ] Issue status updated in issues.jsonl (in_progress -> resolved or open on failure)
 - [ ] Result summary displayed with next-step routing:
-  - Execution succeeded → Skill({ skill: "manage-issue", args: "close <ISS-ID> --resolution fixed" })
-  - Execution failed → Skill({ skill: "quality-debug", args: "<failure description>" }) then retry
-  - Want verification → Skill({ skill: "maestro-verify", args: "{phase}" })
+  - Execution succeeded → `/manage-issue close <ISS-ID> --resolution fixed`
+  - Execution failed → `/quality-debug <failure description>` then retry
+  - Want verification → `/maestro-verify {phase}`
 </success_criteria>

package/.claude/commands/manage-issue.md

@@ -48,9 +48,9 @@ Parse subcommand from first token of $ARGUMENTS.
 Follow '~/.maestro/workflows/issue.md' completely.
 
 **Next-step routing on completion:**
-- create → Skill({ skill: "manage-issue-analyze", args: "<ISS-ID>" }) or Skill({ skill: "manage-issue-plan", args: "<ISS-ID>" })
-- list → Skill({ skill: "manage-issue-analyze", args: "<ISS-ID>" }) for any open issue
-- close → Skill({ skill: "manage-status" })
+- create → `/manage-issue-analyze <ISS-ID>` or `/manage-issue-plan <ISS-ID>`
+- list → `/manage-issue-analyze <ISS-ID>` for any open issue
+- close → `/manage-status`
 </execution>
 
 <error_codes>
@@ -67,7 +67,7 @@ Follow '~/.maestro/workflows/issue.md' completely.
 - [ ] Output displayed in appropriate format (table for list, detail for status)
 - [ ] Cross-references maintained (link creates bidirectional references)
 - [ ] Next step routing by subcommand:
-  - create → Skill({ skill: "manage-issue-analyze", args: "<ISS-ID>" }) or Skill({ skill: "manage-issue-plan", args: "<ISS-ID>" })
-  - list → Skill({ skill: "manage-issue-analyze", args: "<ISS-ID>" }) for any open issue
-  - close → Skill({ skill: "manage-status" })
+  - create → `/manage-issue-analyze <ISS-ID>` or `/manage-issue-plan <ISS-ID>`
+  - list → `/manage-issue-analyze <ISS-ID>` for any open issue
+  - close → `/manage-status`
 </success_criteria>

package/.claude/commands/manage-learn.md

@@ -1,7 +1,7 @@
 ---
 name: manage-learn
-description: Capture, search, and review atomic learning insights into .workflow/learning/lessons.jsonl
-argument-hint: "[<text>|list|search|show <id>] [--category ...] [--tag t1,t2] [--phase N] [--confidence ...]"
+description: Capture, search, and review atomic learning insights and tips into .workflow/learning/lessons.jsonl
+argument-hint: "[<text>|tip <text>|list|search|show <id>] [--category ...] [--tag t1,t2] [--phase N] [--confidence ...]"
 allowed-tools:
   - Read
   - Write
@@ -12,7 +12,11 @@ allowed-tools:
   - AskUserQuestion
 ---
 <purpose>
-Atomic insight capture for the workflow learning library. Lightweight gstack-style "eureka moment" log that complements `quality-retrospective`: where retrospective extracts insights from a completed phase in bulk, `manage-learn` captures one timeless insight at a time during active work. Insights are appended to `.workflow/learning/lessons.jsonl` with auto-detected phase linkage and a simple keyword-based category inference. Same store as retrospective output, so search and list see both manual captures and retrospective-distilled insights.
+Unified atomic knowledge capture for the workflow learning library. Captures two types of knowledge:
+- **Insights**: Timeless "eureka moment" entries (patterns, gotchas, techniques) — the default mode
+- **Tips**: Quick contextual notes for cross-session recovery (formerly in `manage-memory-capture tip`)
+
+Both types are stored in `.workflow/learning/lessons.jsonl` with auto-detected phase linkage and keyword-based category inference. Tips are distinguished by `source: "tip"` and implicitly tagged `tip`. Same store as retrospective output, so search and list see the entire knowledge corpus.
 </purpose>
 
 <required_reading>
@@ -23,30 +27,31 @@ Atomic insight capture for the workflow learning library. Lightweight gstack-sty
 Arguments: $ARGUMENTS
 
 **Modes (auto-detected from first token):**
-- `"<insight text>"` (or any non-keyword text) → capture mode
-- `list` → list recent insights (default 20)
+- `"<insight text>"` (or any non-keyword text) → insight capture mode
+- `tip <text>` → tip capture mode (quick contextual note, auto-tagged `tip`)
+- `list` → list recent entries (default 20)
 - `search <query>` → text search across lessons.jsonl
-- `show <INS-id>` → full insight detail with phase context
-- empty → AskUserQuestion to prompt for insight text
+- `show <INS-id>` → full detail with phase context
+- empty → AskUserQuestion to prompt for text
 
-**Capture flags:**
-- `--category <name>` — pattern | antipattern | decision | tool | gotcha | technique. Default: inferred from text via keyword heuristics.
-- `--tag t1,t2` — comma-separated tags. Always implicitly adds `manual`.
+**Capture flags (both insight and tip modes):**
+- `--category <name>` — pattern | antipattern | decision | tool | gotcha | technique | tip. Default: inferred from text via keyword heuristics. Tip mode defaults to `tip`.
+- `--tag t1,t2` — comma-separated tags. Insight mode implicitly adds `manual`, tip mode implicitly adds `tip`.
 - `--phase <N>` — override auto-detected current phase. Use `--phase 0` to force "no phase".
-- `--confidence <level>` — high | medium | low. Default: medium.
+- `--confidence <level>` — high | medium | low. Default: medium (insight), low (tip).
 
 **List/search flags:**
 - `--tag t1,t2` — filter by tag
 - `--category <name>` — filter by category
 - `--phase <N>` — filter by phase
-- `--lens <name>` — filter by retrospective lens (technical | process | quality | decision)
+- `--lens <name>` — filter by retrospective lens (technical | process | quality | decision | git). Note: `git` matches `source: "retro-git"` from learn-retro; others match `lens` field from quality-retrospective.
 - `--limit <N>` — list mode row limit (default 20)
 
 **Storage:**
 - `.workflow/learning/lessons.jsonl` — append-only JSONL row per insight (shared with `quality-retrospective` output)
 - `.workflow/learning/learning-index.json` — searchable index (mirrors `memory-index.json` schema)
 
-**Shared store rationale:** Manual captures (`source: "manual"`, `lens: null`) and retrospective-distilled insights (`source: "retrospective"`, `lens: <name>`) live side by side so search and list see the entire knowledge corpus. The `source` and `lens` fields disambiguate.
+**Shared store rationale:** Manual captures (`source: "manual"`), tips (`source: "tip"`), retrospective-distilled insights (`source: "retrospective"`, `lens: <name>` from `quality-retrospective`), and learn-retro insights (`source: "retro-git"` or `source: "retro-decision"` from `learn-retro`) all live in the same store so search and list see the entire knowledge corpus. The `source` field disambiguates origin.
 </context>
 
 <execution>
@@ -55,16 +60,17 @@ Follow `~/.maestro/workflows/learn.md` Stages 1–5 in order. Key invariants:
 1. **No agent or CLI calls** — this is a pure file operation: parse → infer → append → confirm. Category inference is keyword-based, not LLM-based.
 2. **Auto-link phase** — read `.workflow/state.json` for `current_phase` and resolve the matching directory slug. `--phase 0` forces no link.
 3. **Match memory-index pattern** — `learning-index.json` schema mirrors `memory-index.json` from `workflows/memory.md` (entries[] with id, type, timestamp, file, summary, tags, plus learn-specific fields: lens, category, phase, phase_slug, confidence, routed_to, routed_id).
-4. **Stable INS ids** — `INS-{8 lowercase hex}` from `hash(insight_text + timestamp)`.
+4. **Stable INS ids** — `INS-{8 lowercase hex}` from `hash(insight_text + category + phase)`. Deterministic: same content in same context always produces the same ID.
 5. **Append-only lessons.jsonl** — never rewrite existing rows; duplicate detection is the user's job at search time.
 6. **Bootstrap on demand** — create `.workflow/learning/`, `lessons.jsonl`, `learning-index.json` on first use; do not require them to exist upfront.
+7. **Tip mode** — when first token is `tip`, set `source: "tip"`, `category: "tip"`, `confidence: "low"`, and implicitly add `tip` tag. Everything else follows the same pipeline as insight capture. This replaces the former `manage-memory-capture tip` mode.
 </execution>
 
 <error_codes>
 | Code | Severity | Description | Stage |
 |------|----------|-------------|-------|
-| E001 | error | `.workflow/` not initialized — run `Skill({ skill: "maestro-init" })` first | parse_input |
-| E002 | error | Unknown `--category` value (allowed: pattern, antipattern, decision, tool, gotcha, technique) | parse_input |
+| E001 | error | `.workflow/` not initialized — run `/maestro-init` first | parse_input |
+| E002 | error | Unknown `--category` value (allowed: pattern, antipattern, decision, tool, gotcha, technique, tip) | parse_input |
 | E003 | error | `show` mode requires an INS-id argument | show |
 | E004 | error | Insight id not found in lessons.jsonl | show |
 | W001 | warning | Auto-phase detection found a current_phase but no matching directory; phase set to null | capture |
@@ -82,5 +88,5 @@ Follow `~/.maestro/workflows/learn.md` Stages 1–5 in order. Key invariants:
 - [ ] Show: full insight displayed with phase context and routed-artifact link if any
 - [ ] No file modifications outside `.workflow/learning/`
 - [ ] Confirmation banner displayed with INS-id and next-step hints
-- [ ] Next step: `Skill({ skill: "manage-learn", args: "list" })` to browse, or `Skill({ skill: "manage-learn", args: "search <query>" })` to find related insights
+- [ ] Next step: `/manage-learn list` to browse, or `/manage-learn search <query>` to find related insights
 </success_criteria>

package/.claude/commands/manage-memory-capture.md

@@ -1,7 +1,7 @@
 ---
 name: manage-memory-capture
-description: Capture session memory (compact or tips) into .workflow/memory/ with JSON index
-argument-hint: "[compact|tip] [description] [--tag tag1,tag2]"
+description: Capture session memory (compact mode) into .workflow/memory/ with JSON index
+argument-hint: "[compact] [description]"
 allowed-tools:
   - Read
   - Write
@@ -12,7 +12,9 @@ allowed-tools:
   - AskUserQuestion
 ---
 <purpose>
-Capture session working memory into `.workflow/memory/` for cross-session recovery. Supports two modes: compact (full session compression for recovery) and tip (quick note-taking with tags). Maintains a `memory-index.json` for search and retrieval. Invoked when saving session state before context loss or recording insights during work.
+Capture session working memory into `.workflow/memory/` for cross-session recovery. Compact mode only: full session compression for recovery. Maintains a `memory-index.json` for search and retrieval. Invoked when saving session state before context loss.
+
+**Note:** Quick tips/notes have been moved to `manage-learn tip <text>`. Use that command for atomic knowledge capture.
 </purpose>
 
 <required_reading>
@@ -22,13 +24,9 @@ Capture session working memory into `.workflow/memory/` for cross-session recove
 <context>
 Arguments: $ARGUMENTS
 
-**Modes:**
+**Mode:**
 - `compact` — Full session memory compression (files, decisions, plan state, pending work)
-- `tip` — Quick note with optional tags and context
-- No arguments — Auto-detect or ask user
-
-**Flags:**
-- `--tag tag1,tag2` — Categorization tags (tip mode)
+- No arguments — Defaults to compact mode
 
 **Storage:**
 - `.workflow/memory/` — Memory entries directory
@@ -42,20 +40,20 @@ Follow '~/.maestro/workflows/memory.md' Part B (Memory Capture) completely.
 <error_codes>
 | Code | Severity | Description | Stage |
 |------|----------|-------------|-------|
-| E001 | error | `.workflow/` not initialized — run Skill({ skill: "maestro-init" }) first | parse_input |
-| E002 | error | Empty note content in tip mode — provide text to save | parse_input |
+| E001 | error | `.workflow/` not initialized — run `/maestro-init` first | parse_input |
+| E002 | error | Tip mode removed — use `/manage-learn tip <text>` instead | parse_input |
 | W001 | warning | No active workflow session found — compact will capture conversation only | analyze_session |
 | W002 | warning | Plan detection found no explicit plan — using inferred plan | analyze_session |
 </error_codes>
 
 <success_criteria>
-- [ ] Mode correctly detected (compact or tip)
+- [ ] Compact mode executed
 - [ ] Entry markdown file written to `.workflow/memory/`
 - [ ] `memory-index.json` updated with new entry metadata
-- [ ] Compact: all session fields populated (objective, files, decisions, plan)
-- [ ] Compact: execution plan preserved VERBATIM (not summarized)
-- [ ] Compact: all file paths are ABSOLUTE
-- [ ] Tip: content, tags, and context captured
+- [ ] All session fields populated (objective, files, decisions, plan)
+- [ ] Execution plan preserved VERBATIM (not summarized)
+- [ ] All file paths are ABSOLUTE
 - [ ] Confirmation banner displayed with entry ID
-- [ ] Next step: Skill({ skill: "manage-status" }) to resume workflow, or Skill({ skill: "manage-memory", args: "view <entry_id>" }) to verify captured memory
+- [ ] Next step: `/manage-status` to resume workflow, or `/manage-memory view <entry_id>` to verify captured memory
+- [ ] For tips: redirect user to `/manage-learn tip <text>`
 </success_criteria>

package/.claude/commands/manage-memory.md

@@ -30,7 +30,7 @@ Arguments: $ARGUMENTS
 
 | Store | Path | Format | Index |
 |-------|------|--------|-------|
-| `workflow` | `.workflow/memory/` | `MEM-*.md`, `TIP-*.md` | `memory-index.json` |
+| `workflow` | `.workflow/memory/` | `MEM-*.md`, `TIP-*.md` (legacy only — new tips go to `manage-learn tip`) | `memory-index.json` |
 | `system` | `~/.claude/projects/{project}/memory/` | `MEMORY.md` + topic `.md` files | None (flat files) |
 
 **System memory path detection:**
@@ -64,7 +64,7 @@ Follow '~/.maestro/workflows/memory.md' Part A (Memory Management) completely.
 <error_codes>
 | Code | Severity | Description | Stage |
 |------|----------|-------------|-------|
-| E001 | error | No memory stores found — run Skill({ skill: "manage-memory-capture" }) or create MEMORY.md | resolve_paths |
+| E001 | error | No memory stores found — run `/manage-memory-capture` or create MEMORY.md | resolve_paths |
 | E002 | error | Entry ID or filename not found | execute_view, execute_delete |
 | E003 | error | Prune requires at least one filter (--tag, --type, --before, --after) | execute_prune |
 | E004 | error | Cannot delete MEMORY.md — use `edit` subcommand instead | execute_delete |
@@ -84,5 +84,5 @@ Follow '~/.maestro/workflows/memory.md' Part A (Memory Management) completely.
 - [ ] Delete: MEMORY.md protected, confirmation required, references checked
 - [ ] Prune: workflow-only, filters validated, index updated
 - [ ] Integrity check catches orphans and broken links
-- [ ] Next step: Skill({ skill: "manage-memory-capture", args: "compact" }) to save new memory, or Skill({ skill: "manage-status" }) to continue workflow
+- [ ] Next step: `/manage-memory-capture compact` to save new memory, or `/manage-status` to continue workflow
 </success_criteria>