maestro-flow 0.3.14 → 0.3.16

package/.claude/commands/maestro-spec-generate.md

@@ -29,32 +29,8 @@ This is the heavy-path entry for structured decomposition: idea → spec-generat
 <context>
 $ARGUMENTS -- idea text, @file reference to requirements document, or brainstorm session reference.
 
-**Flags:**
-- `-y` / `--yes`: Auto mode — skip interactive questions, use recommended defaults
-- `-c` / `--continue`: Resume from last checkpoint (reads spec-config.json)
-- `--count N`: Limit number of exploration dimensions (default 5)
-- `--from-brainstorm SESSION-ID`: Import guidance-specification.md from a brainstorm session as seed
+Flags, input types, output location, and pipeline position defined in workflow spec-generate.md.
 
-**Input types:**
-- Direct text: `"Build a real-time collaboration platform"`
-- File reference: `@requirements.md` or `@design-brief.txt`
-- Brainstorm import: `--from-brainstorm WFS-xxx` (reads `.workflow/scratch/brainstorm-*/`)
-
-**Output location:** `.workflow/.spec/SPEC-{slug}-{YYYY-MM-DD}/`
-
-**Relationship to pipeline:**
-```
-maestro-brainstorm (optional upstream)
-        ↓ guidance-specification.md
-maestro-init (REQUIRED first step — project setup)
-        ↓ project.md, state.json, config.json
-maestro-spec-generate (this command — heavy path)
-        ↓ spec package + roadmap.md → .workflow/roadmap.md
-maestro-plan → maestro-execute → maestro-verify
-
-Alternative light path (skip spec-generate):
-maestro-init → maestro-roadmap → roadmap.md directly
-```
 **Note:** `maestro-init` MUST run before this command. It creates the `.workflow/` directory and project context that spec-generate builds upon.
 </context>
 

package/.claude/commands/maestro-ui-design.md

@@ -33,86 +33,27 @@ Position in pipeline: analyze -> **ui-design** -> plan -> execute -> verify
 <context>
 $ARGUMENTS — phase number for phase mode, topic text for scratch mode, with optional flags.
 
-**Flags:**
-- `--styles N` — Number of style variants to generate (default: 3, range: 2-5)
-- `--layouts N` — Number of layout variants per target (default: 2, range: 1-3)
-- `--stack <stack>` — Tech stack for implementation guidelines (default: html-tailwind). Options: html-tailwind, react, nextjs, vue, svelte, shadcn
-- `--targets <pages>` — Comma-separated page/component targets to prototype (default: inferred from phase goal or "home")
-- `--refine` — Refinement mode: fine-tune an existing design-ref instead of generating from scratch (ui-design.md only)
-- `--persist` — Save design system with hierarchical page overrides (MASTER.md + pages/)
-- `--full` — Force full 4-layer pipeline (ui-design.md) even when ui-ux-pro-max is available
-- `-y` / `--yes` — Auto mode: skip interactive selection, pick top-scored variant
-
-**Workflow routing:**
-- Default: auto-detect ui-ux-pro-max skill → if found, use `ui-style.md` (lightweight); if not, use `ui-design.md` (self-contained)
-- `--full`: always use `ui-design.md` regardless of skill availability
-- Flags `--layouts N` and `--refine` are only effective with `ui-design.md` (full pipeline)
+Flags, workflow routing, scope modes, and output artifacts defined in the routed workflow (ui-style.md or ui-design.md).
 
 **Phase mode** (number): resolves phase directory, reads context.md/brainstorm for requirements.
 **Scratch mode** (text): creates `.workflow/scratch/{YYYYMMDD}-ui-design-{slug}/` for standalone exploration.
-
-**Output artifacts (in phase or scratch directory):**
-| Artifact | Description |
-|----------|-------------|
-| `design-ref/` | Root directory for all design outputs |
-| `design-ref/MASTER.md` | Selected design system (colors, typography, spacing, effects, anti-patterns) |
-| `design-ref/design-tokens.json` | Production-ready tokens (OKLCH colors, typography.combinations, component_styles, opacity) |
-| `design-ref/animation-tokens.json` | Animation system (duration, easing, transitions, keyframes, interactions) |
-| `design-ref/layout-templates/` | Structural layout templates per target (dom_structure + css_layout_rules) |
-| `design-ref/prototypes/` | Assembled HTML/CSS prototypes (styles x layouts x targets) |
-| `design-ref/prototypes/compare.html` | Interactive matrix comparison page |
-| `design-ref/.intermediates/` | Analysis options, user selections, exploration data |
-| `design-ref/selection.json` | User selection metadata + rationale |
-| `design-ref/pages/{page}.md` | Page-specific design overrides (if --persist) |
 </context>
 
 <execution>
-## Workflow Routing (skill detection)
-
-Detect ui-ux-pro-max skill availability:
-
-```bash
-SKILL_PATH=""
-for path in \
-  "skills/ui-ux-pro-max/scripts/search.py" \
-  "$HOME/.claude/plugins/cache/ui-ux-pro-max-skill/ui-ux-pro-max/*/scripts/search.py"; do
-  expanded=$(ls $path 2>/dev/null | tail -1)
-  if [ -n "$expanded" ]; then SKILL_PATH="$expanded"; break; fi
-done
-[ -z "$SKILL_PATH" ] && SKILL_PATH=$(find "$HOME/.claude/plugins" -path "*/ui-ux-pro-max/*/scripts/search.py" -print -quit 2>/dev/null)
-```
-
-**Route:**
+## Workflow Routing
+
+Detect ui-ux-pro-max skill availability and route to the appropriate workflow:
+
 - **`--full` flag present** → Follow '~/.maestro/workflows/ui-design.md' completely (forced full pipeline)
-- **SKILL_PATH found** → Follow '~/.maestro/workflows/ui-style.md' completely (lightweight, delegates design to ui-ux-pro-max)
-- **SKILL_PATH empty** → Follow '~/.maestro/workflows/ui-design.md' completely (self-contained 4-layer pipeline fallback)
-
-Pass `SKILL_PATH` to the workflow when using ui-style.md.
-
-**Report format on completion:**
-
-```
-=== UI DESIGN READY ===
-Phase:   {phase_name}
-Styles:  {style_count} variants, #{selected} selected
-Layouts: {layout_count} per target
-Targets: {target_list}
-Stack:   {stack}
-Matrix:  {S x L x T} = {total} prototypes
-
-Design System:
-  MASTER.md:        {scratch_dir}/design-ref/MASTER.md
-  Tokens:           {scratch_dir}/design-ref/design-tokens.json
-  Animation:        {scratch_dir}/design-ref/animation-tokens.json
-  Layout Templates: {scratch_dir}/design-ref/layout-templates/
-  Prototypes:       {scratch_dir}/design-ref/prototypes/
-  Compare:          {scratch_dir}/design-ref/prototypes/compare.html
-
-Next steps:
-  /maestro-plan {phase}              -- Plan with design reference
-  /maestro-ui-design {phase} --refine -- Refine selected design
-  /maestro-analyze {phase}           -- Analyze before planning
-```
+- **ui-ux-pro-max found** → Follow '~/.maestro/workflows/ui-style.md' completely (lightweight delegation)
+- **ui-ux-pro-max not found** → Follow '~/.maestro/workflows/ui-design.md' completely (self-contained fallback)
+
+Skill detection logic, report format, and complete pipeline steps defined in the routed workflow file.
+
+**Next-step routing on completion:**
+- Plan with design reference → /maestro-plan {phase}
+- Refine selected design → /maestro-ui-design {phase} --refine
+- Analyze before planning → /maestro-analyze {phase}
 </execution>
 
 <error_codes>

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

@@ -37,38 +37,7 @@ Registers VRF artifact in state.json on completion.
 <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/{YYYYMMDD}-verify-M{N}-{slug}/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/{YYYYMMDD}-verify-M{N}-{slug}",  // M{N} = milestone number
-  "status": "completed",
-  "depends_on": ["EXC-001", "EXC-002", ...],
-  "harvested": false,
-  "created_at": "...",
-  "completed_at": "..."
-}
-```
+Flags (`--skip-tests`, `--skip-antipattern`, `--dir`), scope routing, output paths, and VRF artifact registration schema are defined in workflow `verify.md`.
 </context>
 
 <execution>

package/.claude/commands/maestro.md

@@ -1,10 +1,11 @@
 ---
 name: maestro
-description: Intelligent coordinator - analyze intent + read project state → select optimal command chain → execute via Skill()
-argument-hint: "\"intent text\" [-y] [-c] [--dry-run] [--chain <name>]"
+description: Intelligent coordinator - analyze intent + read project state → select optimal command chain → execute via Skill() or CLI delegate
+argument-hint: "\"intent text\" [-y] [-c] [--dry-run] [--chain <name>] [--exec auto|cli|skill] [--tool <name>]"
 allowed-tools:
   - Read
   - Write
+  - Edit
   - Bash
   - Glob
   - Grep
@@ -17,6 +18,10 @@ Two routing modes:
 1. **Intent-based**: User describes a goal → classify task type → select/compose command chain → confirm → execute
 2. **State-based**: Read .workflow/state.json → determine next logical step → suggest/execute (triggered by `continue`/`next`)
 
+Per-step execution engine (default: auto):
+- **Skill()**: Observable steps — output visible in conversation, synchronous, user can intervene
+- **CLI delegate**: Heavy execution steps — context isolation, template-driven prompts, gemini quality analysis
+
 Produces session directory at `.workflow/.maestro/{session_id}/` with status.json tracking chain progress.
 Executes commands sequentially via Skill() with artifact propagation between steps.
 </purpose>
@@ -37,6 +42,8 @@ $ARGUMENTS — user intent text, or special keywords.
 - `-c` / `--continue` — Resume previous coordinator session from `.workflow/.maestro/*/status.json`
 - `--dry-run` — Show planned chain without executing
 - `--chain <name>` — Force a specific chain (bypass intent detection). Valid: full-lifecycle, spec-driven, brainstorm-driven, execute-verify, quality-loop, milestone-close, quick, review
+- `--exec <mode>` — Execution engine: `auto` (default), `cli`, `skill`. Auto selects per step based on command complexity.
+- `--tool <name>` — CLI tool for delegate execution (default: claude). Only used when engine=cli.
 
 **State files read:**
 - `.workflow/state.json` — project state machine + artifact registry
@@ -76,32 +83,7 @@ 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:
-- `-y` active → print one-line warning and continue.
-- Otherwise → stop before the next step and ask the user (Continue / Pause to resume with `-c` / Abort). Wait for explicit choice.
-
-**Report format on completion:**
-
-```
-=== MAESTRO SESSION COMPLETE ===
-Session: {session_id}
-Chain:   {chain_name} ({steps_completed}/{steps_total} steps)
-Milestone: {current_milestone} (if applicable)
-Mode:    {auto | interactive}
-
-Steps:
-  [{status_icon}] {N}. {command_name} — {duration}
-
-Next: {suggested_next_action}
-```
+Context cleanup hints, context window reminders, and completion report format are defined in workflow maestro.md (Steps 7a-1, 7f).
 </execution>
 
 <error_codes>
@@ -121,10 +103,11 @@ Next: {suggested_next_action}
 - [ ] Intent classified with task_type, complexity, clarity_score
 - [ ] Project state read and incorporated into routing
 - [ ] Command chain selected and confirmed (or auto-confirmed with -y)
+- [ ] Per-step engine selected (auto routes heavy steps to CLI, observable steps to Skill)
 - [ ] Auto flags correctly propagated to supporting commands only
 - [ ] Session directory created at .workflow/.maestro/{session_id}/
-- [ ] status.json tracks per-step progress
-- [ ] All chain steps executed via Skill() with proper argument propagation
+- [ ] status.json tracks per-step progress and execution engine
+- [ ] All chain steps executed via Skill() or CLI delegate with proper argument propagation
 - [ ] Phase numbers auto-detected and passed to downstream commands
 - [ ] Error handling: retry/skip/abort per step (auto-skip in -y mode)
 - [ ] Session summary displayed on completion

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

@@ -37,55 +37,18 @@ Arguments: $ARGUMENTS
 - `<session-id>` (e.g., `ANL-auth-20260410`, `WFS-xxx`) → `session` mode: harvest specific session
 - `<path>` (e.g., `.workflow/.analysis/ANL-auth-20260410/`) → `path` mode: harvest from explicit directory
 
-**Flags:**
-- `--to <target>` — Force routing: `wiki`, `spec`, `issue`, `auto` (default: `auto`)
-- `--source <type>` — Filter source type: `analysis`, `brainstorm`, `debug`, `lite-plan`, `lite-fix`, `scratchpad`, `session`, `learning`, `all` (default: `all`)
-- `--recent N` — Only artifacts updated within last N days (default: 30)
-- `--dry-run` — Preview extraction and routing without writing
-- `-y` / `--yes` — Skip confirmation prompts
-- `--min-confidence N` — Minimum extraction confidence 0.0-1.0 (default: 0.5)
-
-**Source registry (scan paths):**
-| Source Type | Scan Path | Key Files |
-|-------------|-----------|-----------|
-| `analysis` | `.workflow/.analysis/ANL-*/` | `conclusions.json`, `*.md` |
-| `brainstorm` | `.workflow/scratch/brainstorm-*/` | `guidance-specification.md` |
-| `lite-plan` | `.workflow/.lite-plan/*/` | `plan.json`, `plan-overview.md` |
-| `lite-fix` | `.workflow/.lite-fix/*/` | `fix-plan.json` |
-| `debug` | `.workflow/.debug/*/` | `debug-log.md`, `hypothesis-*.md` |
-| `scratchpad` | `.workflow/.scratchpad/` | `*.md`, `*.json` |
-| `session` | `.workflow/active/WFS-*/` | `workflow-session.json` |
-| `learning` | `.workflow/learning/` | `lessons.jsonl`, `digest-*.md` |
-
-**Storage written:**
-- `.workflow/harvest/harvest-log.jsonl` — provenance log (prevents duplicate harvesting)
-- `.workflow/harvest/harvest-report-{date}.md` — per-run report
-- Wiki entries via `maestro wiki create`
-- Spec entries via `Skill({ skill: "spec-add" })`
-- Issue entries appended to `.workflow/issues/issues.jsonl`
-
-**Storage read (never modified):**
-- All artifact source files (read-only until routing stage)
-- `.workflow/harvest/harvest-log.jsonl` (dedup check)
+Flags, source registry (scan paths), and storage locations defined in workflow harvest.md.
 </context>
 
 <execution>
-Follow '~/.maestro/workflows/harvest.md' Stages 1–8 in order. Key invariants:
-
-1. **Read-only until Stage 6** — Stages 1–5 must not write anything. All extraction and classification happens in-memory.
-2. **Dedup before write** — Stage 7 (dedup_check) runs BEFORE each write in Stage 6. Check harvest-log.jsonl, wiki search, issues.jsonl, and learnings.md for existing matches.
-3. **Stable fragment IDs** — `HRV-{8 hex}` from `hash(source_id + content_hash)` so re-runs on same artifacts do not create duplicates.
-4. **Reuse existing routing infrastructure**:
-   - Wiki: `maestro wiki create --type <type> --slug harvest-<source_type>-<short_id> --created-by manage-harvest --source-ref HRV-<fragment_id> --category <fragment_category>`
-   - Spec: `Skill({ skill: "spec-add", args: "<category> <content>" })`
-   - Issue: append to `issues.jsonl` matching canonical schema from `workflows/issue.md`
-5. **Never modify source artifacts** — harvest is purely extractive. Source files remain untouched.
-6. **Confidence filtering** — fragments below `--min-confidence` are logged but not routed.
-7. **Provenance tracking** — every routed item logged to `harvest-log.jsonl` with fragment_id, source reference, and target reference.
+Follow '~/.maestro/workflows/harvest.md' Stages 1-8 in order.
 
-**Fragment extraction uses source-specific parsing** (see harvest.md Stage 3b for per-source patterns). The agent should read each artifact file and identify discrete knowledge items: findings, decisions, patterns, bugs, risks, tasks, lessons, recommendations.
+**Key invariants:**
+1. **Read-only until Stage 6** — extraction and classification happen in-memory.
+2. **Dedup before write** — check harvest-log.jsonl and existing stores before each write.
+3. **Never modify source artifacts** — harvest is purely extractive.
 
-**Classification uses category-to-target mapping** (see harvest.md Stage 4). Override with `--to` flag if user wants all items in one store.
+Extraction patterns, classification rules, routing infrastructure, and fragment ID scheme defined in workflow harvest.md.
 
 **Next-step routing on completion:**
 - Review wiki entries → `maestro wiki list --type note`

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

@@ -0,0 +1,193 @@
+---
+name: manage-knowhow-capture
+description: Capture reusable knowledge into .workflow/knowhow/ — session compact, template, recipe, reference, decision, or tip
+argument-hint: "[type] [description] [--lang <lang>] [--source <url>] [--tag tag1,tag2]"
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Bash
+  - Glob
+  - Grep
+  - AskUserQuestion
+---
+<purpose>
+Capture reusable knowledge into `.workflow/knowhow/` with type-specific structured fields.
+Six content types, each optimized for a different reuse pattern. All entries are automatically
+indexed by WikiIndexer (type=knowhow) and searchable via `maestro knowhow search`.
+</purpose>
+
+<required_reading>
+@~/.maestro/workflows/knowhow.md
+</required_reading>
+
+<context>
+Arguments: $ARGUMENTS
+
+**Types:**
+
+| Type | Prefix | Use Case | Key Fields |
+|------|--------|----------|------------|
+| `compact` | KNW- | Session state recovery | objective, files, decisions, plan, pending |
+| `template` | TPL- | Code/config templates | language, code block, usage context |
+| `recipe` | RCP- | Step-by-step how-to | prerequisites, steps, expected outcome |
+| `reference` | REF- | External doc / API quick-ref | source URL, key points, scenarios |
+| `decision` | DCS- | Design decision record | context, alternatives, rationale, consequences |
+| `tip` | TIP- | Quick note / reminder | content, tags |
+
+No arguments: auto-detect type or ask user via AskUserQuestion.
+
+**Flags:**
+- `--lang <lang>` — Language for templates (typescript, python, bash, yaml, etc.)
+- `--source <url>` — Source URL for references
+- `--tag tag1,tag2` — Categorization tags
+- `--title <title>` — Explicit title (auto-generated if omitted)
+</context>
+
+<execution>
+
+### Step 1: Detect Type
+
+Parse first token as type. If ambiguous, AskUserQuestion with options:
+
+| Token Match | Type |
+|-------------|------|
+| `compact`, `session`, `压缩`, `保存` | compact |
+| `template`, `tpl`, `模板` | template |
+| `recipe`, `rcp`, `配方`, `步骤` | recipe |
+| `reference`, `ref`, `参考`, `引用` | reference |
+| `decision`, `dcs`, `决策`, `adr` | decision |
+| `tip`, `note`, `记录`, `快速` | tip |
+| No match, short text, `--tag` present | tip |
+| No arguments | AskUserQuestion (6 options) |
+
+### Step 2: Generate Content by Type
+
+#### compact (KNW-{YYYYMMDD}-{HHMM}.md)
+
+Extract from conversation history:
+- **Session ID** — WFS-* if workflow session active, else `manual-{date}`
+- **Project Root** — Absolute path
+- **Objective** — High-level goal
+- **Execution Plan** — Source + complete verbatim content (never summarize)
+- **Working Files** — Modified files with roles (absolute paths, 3-8 files)
+- **Reference Files** — Read-only context files
+- **Last Action** — Final action + result
+- **Decisions** — Table: decision | reasoning
+- **Constraints** — User-specified limitations
+- **Dependencies** — Added/changed packages
+- **Known Issues** — Deferred bugs
+- **Changes Made** — Completed modifications
+- **Pending** — Next steps
+- **Notes** — Unstructured thoughts
+
+Plan detection priority: workflow session IMPL_PLAN.md > TodoWrite items > user-stated > inferred.
+
+#### template (TPL-{YYYYMMDD}-{HHMM}.md)
+
+Ask for or extract:
+- **Language / Tech** — `--lang` flag or inferred from context
+- **Usage** — When/how to use this template
+- **Code** — The template content (ask user to provide or select from conversation)
+- **Parameters** — Placeholders to replace (e.g. `{{name}}`, `{{port}}`)
+- **Dependencies** — Required packages/config
+- **Tags** — From `--tag` flag
+
+If code not provided explicitly, prompt user: "Paste the template code:"
+
+#### recipe (RCP-{YYYYMMDD}-{HHMM}.md)
+
+Ask for or extract:
+- **Goal** — What this recipe accomplishes
+- **Prerequisites** — Tools, access, config needed
+- **Steps** — Numbered step-by-step instructions
+- **Expected Outcome** — What success looks like
+- **Common Pitfalls** — Known issues / gotchas
+- **Related** — Links to templates, references, decisions used
+- **Tags** — From `--tag` flag
+
+If steps not clear, prompt user: "Describe the steps (numbered list):"
+
+#### reference (REF-{YYYYMMDD}-{HHMM}.md)
+
+Ask for or extract:
+- **Source** — `--source` flag (URL, doc title, API endpoint)
+- **Key Points** — Bullet list of essential info
+- **Applicable Scenarios** — When to consult this reference
+- **Quick Examples** — Copy-paste ready code snippets
+- **Last Verified** — Date (today)
+- **Tags** — From `--tag` flag
+
+If `--source` provided, offer to fetch and summarize via WebFetch.
+
+#### decision (DCS-{YYYYMMDD}-{HHMM}.md)
+
+Ask for or extract:
+- **Context** — Background and problem statement
+- **Decision** — What was decided
+- **Alternatives Considered** — Table: alternative | pros | cons | rejected because
+- **Rationale** — Why this choice over alternatives
+- **Consequences** — Positive and negative impact
+- **Related** — Links to affected specs, recipes, templates
+- **Date** — Decision date
+- **Status** — proposed | accepted | superseded
+
+#### tip (TIP-{YYYYMMDD}-{HHMM}.md)
+
+Simple note:
+- **Content** — Everything after type token (or full $ARGUMENTS)
+- **Context** — Auto-detected from recent conversation files
+- **Tags** — From `--tag` flag
+- **Timestamp** — ISO format
+
+### Step 3: Write File
+
+Write to `.workflow/knowhow/{PREFIX}-{YYYYMMDD}-{HHMM}.md` with YAML frontmatter:
+
+```yaml
+---
+title: {auto or --title}
+type: {type}
+category: {type}
+created: {ISO timestamp}
+tags: [{tags}]
+source: {url if reference}
+lang: {language if template}
+status: {status if decision}
+---
+{markdown body}
+```
+
+### Step 4: Confirm
+
+```
+=== KNOWHOW CAPTURED ===
+Type: {type}
+ID:   knowhow-{slug}
+File: .workflow/knowhow/{filename}
+
+{type-specific summary line}
+```
+</execution>
+
+<error_codes>
+| Code | Severity | Description | Stage |
+|------|----------|-------------|-------|
+| E001 | error | `.workflow/` not initialized — run `/maestro-init` first | validate |
+| E002 | error | Template: no code provided after prompt | template |
+| E003 | error | Recipe: no steps provided after prompt | recipe |
+| W001 | warning | No active workflow session — compact captures conversation only | compact |
+| W002 | warning | Plan detection found no explicit plan — using inferred plan | compact |
+| W003 | warning | `--source` URL could not be fetched — proceeding with manual entry | reference |
+</error_codes>
+
+<success_criteria>
+- [ ] Type correctly detected or selected
+- [ ] All type-specific fields populated (not empty)
+- [ ] YAML frontmatter written with correct fields
+- [ ] Markdown body follows type structure
+- [ ] File written to `.workflow/knowhow/` with correct prefix
+- [ ] Auto-indexed by WikiIndexer (type=knowhow)
+- [ ] Confirmation displayed with ID, type, file path
+- [ ] Next step hint appropriate to type shown
+</success_criteria>