maestro-flow 0.5.3 → 0.5.31

package/.agents/skills/learn-follow/SKILL.md

@@ -13,117 +13,117 @@ allowed-tools:
 ---
 <!-- Open-standard mirror generated by scripts/build-agents-standard.mjs — do not edit; re-run after editing .claude/ source. -->
 
-<purpose>
-Guided reading: walk through content section-by-section using forcing questions to extract patterns, identify assumptions, and build an understanding map. Findings persist to `.workflow/specs/learnings.md` as `<spec-entry>` blocks.
-</purpose>
-
-<context>
-$ARGUMENTS — target and optional flags.
-
-**Target resolution** (auto-detected):
-| Input | Resolution |
-|-------|-----------|
-| File path (contains `/` or `\`) | Read source file |
-| Wiki ID (`<type>-<slug>`) | `maestro wiki get <id>` |
-| Topic string | `maestro search "<topic>"` → top result; fallback: Grep src/ |
-
-**Flags**:
-- `--depth shallow` (default): key patterns and structure only
-- `--depth deep`: every function, every branch, every assumption
-- `--save-wiki`: create wiki note entry with reading notes
-
-**Storage read**: target file + wiki forward/backlinks + `coding-conventions.md` + `.workflow/specs/learnings.md` (dedup)
-**Storage write**: `.workflow/knowhow/KNW-follow-{slug}-{date}.md` + append `.workflow/specs/learnings.md`
-</context>
-
-<state_machine>
-
-<states>
-S_RESOLVE      — 解析 target (file/wiki/topic)              PERSIST: —
-S_CONTEXT      — 构建 1-hop 上下文邻域                       PERSIST: —
-S_ORDER        — 确定阅读顺序                                PERSIST: —
-S_READ         — 逐节应用 forcing questions                   PERSIST: —
-S_EXTRACT      — 提取 patterns、cross-ref conventions         PERSIST: —
-S_PERSIST      — 写 understanding map + spec-entry 块         PERSIST: knowhow files
-</states>
-
-<transitions>
-
-S_RESOLVE:
-  → S_CONTEXT     WHEN: target resolved
-  → S_RESOLVE     WHEN: unresolvable                       DO: ask_user with suggestions
-
-S_CONTEXT:
-  → S_ORDER       DO: A_BUILD_CONTEXT_WEB
-
-S_ORDER:
-  → S_READ        DO: A_BUILD_READING_ORDER
-
-S_READ:
-  → S_EXTRACT     DO: A_GUIDED_READ (apply 4 forcing questions per section)
-
-S_EXTRACT:
-  → S_PERSIST     DO: A_EXTRACT_PATTERNS
-
-S_PERSIST:
-  → END           DO: write KNW-follow + append .workflow/specs/learnings.md [+ wiki note if --save-wiki]
-
-</transitions>
-
-<actions>
-
-### A_BUILD_CONTEXT_WEB
-
-| Target type | Context |
-|-------------|---------|
-| Wiki entry | `maestro wiki forward <id>` + `maestro wiki backlinks <id>` → read top 3 related |
-| Code file | Parse imports → dependency files; grep exports → reverse deps; read top 3 dependents (50 lines) |
-| Directory | List files, identify entry points → build reading order: entry → core → utils → tests |
-
-### A_BUILD_READING_ORDER
-
-- Single file: split by function/class/export boundaries
-- Wiki entry: split by markdown headings
-- Directory: order by dependency (entry points first, leaf last)
-- `--depth shallow`: top-level structure only; `--depth deep`: every body and branch
-
-### A_GUIDED_READ
-
-For each section, apply 4 forcing questions:
-
-| # | Question | Extracts |
-|---|----------|----------|
-| 1 | "What pattern is being used here?" | Design patterns, idioms, conventions |
-| 2 | "Why this approach instead of alternatives?" | Trade-offs, rejected options |
-| 3 | "What assumption does this depend on?" | Implicit contracts, input shape, ordering |
-| 4 | "What would break if this changed?" | Fragility, downstream effects |
-
-### A_EXTRACT_PATTERNS
-
-Extract: design patterns (with file:line anchors), naming conventions, error handling approach, data flow, assumptions.
-Cross-ref against `coding-conventions.md`: documented → "confirmed convention", undocumented → "candidate for spec-add".
-
-Write understanding map: Key Concepts, Patterns (table: name/location/convention status), Assumptions, Open Questions, Connections.
-
-</actions>
-
-</state_machine>
-
-<error_codes>
-| Code | Condition | Recovery |
-|------|-----------|----------|
-| W002 | coding-conventions.md not found | All patterns marked "unknown status" |
-| W003 | Target > 1000 lines | Auto-switch to shallow; use --depth deep to override |
-</error_codes>
-
-<success_criteria>
-- [ ] 4 forcing questions applied per section
-- [ ] Patterns extracted with file:line anchors and convention cross-ref
-- [ ] Understanding map + spec-entry blocks written
-</success_criteria>
-
-<next_step_routing>
-- Deep pattern dive → `/learn-decompose <path>`
-- Add to specs → `/spec-add coding <description>`
-- Second opinion → `/learn-second-opinion <file>`
-</next_step_routing>
+<purpose>
+Guided reading: walk through content section-by-section using forcing questions to extract patterns, identify assumptions, and build an understanding map. Findings persist to `.workflow/specs/learnings.md` as `<spec-entry>` blocks.
+</purpose>
+
+<context>
+$ARGUMENTS — target and optional flags.
+
+**Target resolution** (auto-detected):
+| Input | Resolution |
+|-------|-----------|
+| File path (contains `/` or `\`) | Read source file |
+| Wiki ID (`<type>-<slug>`) | `maestro wiki get <id>` |
+| Topic string | `maestro search "<topic>"` → top result; fallback: Grep src/ |
+
+**Flags**:
+- `--depth shallow` (default): key patterns and structure only
+- `--depth deep`: every function, every branch, every assumption
+- `--save-wiki`: create wiki note entry with reading notes
+
+**Storage read**: target file + wiki forward/backlinks + `coding-conventions.md` + `.workflow/specs/learnings.md` (dedup)
+**Storage write**: `.workflow/knowhow/KNW-follow-{slug}-{date}.md` + append `.workflow/specs/learnings.md`
+</context>
+
+<state_machine>
+
+<states>
+S_RESOLVE      — 解析 target (file/wiki/topic)              PERSIST: —
+S_CONTEXT      — 构建 1-hop 上下文邻域                       PERSIST: —
+S_ORDER        — 确定阅读顺序                                PERSIST: —
+S_READ         — 逐节应用 forcing questions                   PERSIST: —
+S_EXTRACT      — 提取 patterns、cross-ref conventions         PERSIST: —
+S_PERSIST      — 写 understanding map + spec-entry 块         PERSIST: knowhow files
+</states>
+
+<transitions>
+
+S_RESOLVE:
+  → S_CONTEXT     WHEN: target resolved
+  → S_RESOLVE     WHEN: unresolvable                       DO: ask_user with suggestions
+
+S_CONTEXT:
+  → S_ORDER       DO: A_BUILD_CONTEXT_WEB
+
+S_ORDER:
+  → S_READ        DO: A_BUILD_READING_ORDER
+
+S_READ:
+  → S_EXTRACT     DO: A_GUIDED_READ (apply 4 forcing questions per section)
+
+S_EXTRACT:
+  → S_PERSIST     DO: A_EXTRACT_PATTERNS
+
+S_PERSIST:
+  → END           DO: write KNW-follow + append .workflow/specs/learnings.md [+ wiki note if --save-wiki]
+
+</transitions>
+
+<actions>
+
+### A_BUILD_CONTEXT_WEB
+
+| Target type | Context |
+|-------------|---------|
+| Wiki entry | `maestro wiki forward <id>` + `maestro wiki backlinks <id>` → read top 3 related |
+| Code file | Parse imports → dependency files; grep exports → reverse deps; read top 3 dependents (50 lines) |
+| Directory | List files, identify entry points → build reading order: entry → core → utils → tests |
+
+### A_BUILD_READING_ORDER
+
+- Single file: split by function/class/export boundaries
+- Wiki entry: split by markdown headings
+- Directory: order by dependency (entry points first, leaf last)
+- `--depth shallow`: top-level structure only; `--depth deep`: every body and branch
+
+### A_GUIDED_READ
+
+For each section, apply 4 forcing questions:
+
+| # | Question | Extracts |
+|---|----------|----------|
+| 1 | "What pattern is being used here?" | Design patterns, idioms, conventions |
+| 2 | "Why this approach instead of alternatives?" | Trade-offs, rejected options |
+| 3 | "What assumption does this depend on?" | Implicit contracts, input shape, ordering |
+| 4 | "What would break if this changed?" | Fragility, downstream effects |
+
+### A_EXTRACT_PATTERNS
+
+Extract: design patterns (with file:line anchors), naming conventions, error handling approach, data flow, assumptions.
+Cross-ref against `coding-conventions.md`: documented → "confirmed convention", undocumented → "candidate for spec-add".
+
+Write understanding map: Key Concepts, Patterns (table: name/location/convention status), Assumptions, Open Questions, Connections.
+
+</actions>
+
+</state_machine>
+
+<error_codes>
+| Code | Condition | Recovery |
+|------|-----------|----------|
+| W002 | coding-conventions.md not found | All patterns marked "unknown status" |
+| W003 | Target > 1000 lines | Auto-switch to shallow; use --depth deep to override |
+</error_codes>
+
+<success_criteria>
+- [ ] 4 forcing questions applied per section
+- [ ] Patterns extracted with file:line anchors and convention cross-ref
+- [ ] Understanding map + spec-entry blocks written
+</success_criteria>
+
+<next_step_routing>
+- Deep pattern dive → `/learn-decompose <path>`
+- Add to specs → `/spec-add coding <description>`
+- Second opinion → `/learn-second-opinion <file>`
+</next_step_routing>

package/.agents/skills/learn-investigate/SKILL.md

@@ -13,142 +13,141 @@ allowed-tools:
 ---
 <!-- Open-standard mirror generated by scripts/build-agents-standard.mjs — do not edit; re-run after editing .claude/ source. -->
 
-<purpose>
-Systematic investigation for understanding questions (not bug-fixing). 4-phase scientific method with scope lock and 3-strike escalation. Produces evidence trails and understanding docs that persist to the learning system.
-
-Unlike `quality-debug` (fix bugs during execution), this answers "how does X work?", "why does Y happen?", "what if Z?".
-</purpose>
-
-<context>
-$ARGUMENTS — question text and optional flags.
-
-**Flags**:
-- `--scope <path>`: Restrict to files under this dir (default: entire project)
-- `--max-hypotheses N`: Max hypotheses before escalation (default: 3)
-
-**Storage write**:
-- `.workflow/knowhow/KNW-investigate-{slug}/evidence.ndjson` — structured evidence (one JSON line per item)
-- `.workflow/knowhow/KNW-investigate-{slug}/understanding.md` — evolving understanding
-- `.workflow/knowhow/KNW-investigate-{slug}/report.md` — final report
-- `.workflow/specs/learnings.md` — appended `<spec-entry>` blocks
-
-**Storage read**: source files in scope + `maestro search` + `.workflow/specs/learnings.md` + `debug-notes.md` + `codebase/architecture.md`
-</context>
-
-<state_machine>
-
-<states>
-S_FRAME          — 解析问题、确定 scope、搜索先验知识          PERSIST: understanding.md (initial)
-S_EVIDENCE       — 系统收集证据                                PERSIST: evidence.ndjson
-S_PATTERN        — 比对已知模式                                PERSIST: understanding.md (patterns)
-S_HYPOTHESIZE    — 生成假设列表                                PERSIST: understanding.md (hypotheses)
-S_CLI_EXPLORE    — CLI 辅助探索（可选）                         PERSIST: evidence.ndjson (append)
-S_TEST           — 逐假设测试                                  PERSIST: evidence.ndjson + understanding.md
-S_ESCALATE       — 3-strike 升级                               PERSIST: —
-S_REPORT         — 综合报告 + persist                          PERSIST: report.md + .workflow/specs/learnings.md
-</states>
-
-<transitions>
-
-S_FRAME:
-  → S_EVIDENCE    DO: A_FRAME_QUESTION
-
-S_EVIDENCE:
-  → S_PATTERN     DO: A_COLLECT_EVIDENCE
-
-S_PATTERN:
-  → S_HYPOTHESIZE DO: match evidence against debug-notes.md + .workflow/specs/learnings.md patterns
-
-S_HYPOTHESIZE:
-  → S_CLI_EXPLORE WHEN: CLI tools enabled AND hypotheses non-trivial    DO: A_FORM_HYPOTHESES
-  → S_TEST        WHEN: no CLI tools OR trivial hypotheses              DO: A_FORM_HYPOTHESES
-
-S_CLI_EXPLORE:
-  → S_TEST        DO: A_CLI_SUPPLEMENT (maestro delegate --role explore --mode analysis, run_in_background, STOP)
-
-S_TEST:
-  → S_REPORT      WHEN: hypothesis confirmed                  DO: A_TEST_HYPOTHESIS
-  → S_REPORT      WHEN: all hypotheses tested (some confirmed) DO: A_TEST_HYPOTHESIS
-  → S_ESCALATE    WHEN: max_hypotheses all failed              DO: A_TEST_HYPOTHESIS
-
-S_ESCALATE:
-  → S_HYPOTHESIZE WHEN: user broadens scope or provides new hypothesis   DO: ask_user
-  → S_REPORT      WHEN: user selects "Escalate" or still stuck          DO: mark INCONCLUSIVE
-
-S_REPORT:
-  → END           DO: A_SYNTHESIZE_REPORT
-
-</transitions>
-
-<actions>
-
-### A_FRAME_QUESTION
-
-1. Parse question, generate slug, create KNW-investigate-{slug}/
-2. Search prior knowledge: `maestro search "<question>"` + search .workflow/specs/learnings.md + read debug-notes.md
-3. Write initial understanding.md (question, prior knowledge summary, scope, timestamp)
-
-### A_COLLECT_EVIDENCE
-
-Parallel evidence gathering:
-1. Code search: Grep keywords from question
-2. File inspection: Read most relevant files
-3. Import tracing: follow dependency chain
-4. Git history: `git log --oneline -10 -- <relevant-files>`
-
-Each item → append evidence.ndjson: `{ts, type (code|git|search|doc), source (file:line), relevance (high|medium|low), content, note}`
-
-### A_FORM_HYPOTHESES
-
-Generate ranked hypotheses: each is specific, testable claim about "how/why".
-Rank by plausibility (evidence strength). Write to understanding.md:
-- `[HIGH]` hypothesis — Evidence: {refs}
-- `[MEDIUM]` hypothesis — Evidence: {refs}
-
-### A_CLI_SUPPLEMENT
-
-```
-maestro delegate "PURPOSE: Gather evidence for hypotheses
-TASK: Trace call chains and data flows per hypothesis | Find corroborating/contradicting patterns
-EXPECTED: JSON [{hypothesis_rank, evidence: [{file, line, supports: bool, explanation}]}]
-" --role explore --mode analysis
-```
-Run_in_background, STOP, wait. On callback: append to evidence.ndjson.
-
-### A_TEST_HYPOTHESIS
-
-For each hypothesis (rank order):
-1. Design test: what evidence would confirm/disprove?
-2. Execute: code trace, targeted search, data inspection
-3. Record: append evidence.ndjson with type: "test"
-4. Update: mark hypothesis confirmed / disproved / inconclusive
-
-### A_SYNTHESIZE_REPORT
-
-Write report.md: Answer (or INCONCLUSIVE), Evidence Trail table, Hypotheses Tested table, Key Learnings, Open Questions.
-Append to .workflow/specs/learnings.md: confirmed → roles="implement", disproved → roles="analyze" (gotcha).
-
-</actions>
-
-</state_machine>
-
-<error_codes>
-| Code | Condition | Recovery |
-|------|-----------|----------|
-| E002 | --scope path not found | Check path |
-| W002 | Very few evidence matches (<3) | Broaden search terms or expand scope |
-| W003 | All hypotheses inconclusive | Investigation marked INCONCLUSIVE |
-</error_codes>
-
-<success_criteria>
-- [ ] Evidence collected and logged to evidence.ndjson (structured NDJSON)
-- [ ] At least 1 hypothesis formed and tested
-- [ ] 3-strike escalation triggered if all fail
-- [ ] Report + spec-entry blocks written
-</success_criteria>
-
-<next_step_routing>
-- Save to specs → `/spec-add debug <finding>`
-- Follow code → `/learn-follow <path>`
-- Decompose patterns → `/learn-decompose <module>`
-</next_step_routing>
+<purpose>
+Systematic investigation for understanding questions (not bug-fixing).
+4-phase scientific method with scope lock, 3-strike escalation, and evidence persistence.
+</purpose>
+
+<context>
+$ARGUMENTS — question text and optional flags.
+
+**Flags**:
+- `--scope <path>`: Restrict to files under this dir (default: entire project)
+- `--max-hypotheses N`: Max hypotheses before escalation (default: 3)
+
+**Storage write**:
+- `.workflow/knowhow/KNW-investigate-{slug}/evidence.ndjson` — structured evidence (one JSON line per item)
+- `.workflow/knowhow/KNW-investigate-{slug}/understanding.md` — evolving understanding
+- `.workflow/knowhow/KNW-investigate-{slug}/report.md` — final report
+- `.workflow/specs/learnings.md` — appended `<spec-entry>` blocks
+
+**Storage read**: source files in scope + `maestro search` + `.workflow/specs/learnings.md` + `debug-notes.md` + `codebase/architecture.md`
+</context>
+
+<state_machine>
+
+<states>
+S_FRAME          — 解析问题、确定 scope、搜索先验知识          PERSIST: understanding.md (initial)
+S_EVIDENCE       — 系统收集证据                                PERSIST: evidence.ndjson
+S_PATTERN        — 比对已知模式                                PERSIST: understanding.md (patterns)
+S_HYPOTHESIZE    — 生成假设列表                                PERSIST: understanding.md (hypotheses)
+S_CLI_EXPLORE    — CLI 辅助探索（可选）                         PERSIST: evidence.ndjson (append)
+S_TEST           — 逐假设测试                                  PERSIST: evidence.ndjson + understanding.md
+S_ESCALATE       — 3-strike 升级                               PERSIST: —
+S_REPORT         — 综合报告 + persist                          PERSIST: report.md + .workflow/specs/learnings.md
+</states>
+
+<transitions>
+
+S_FRAME:
+  → S_EVIDENCE    DO: A_FRAME_QUESTION
+
+S_EVIDENCE:
+  → S_PATTERN     DO: A_COLLECT_EVIDENCE
+
+S_PATTERN:
+  → S_HYPOTHESIZE DO: match evidence against debug-notes.md + .workflow/specs/learnings.md patterns
+
+S_HYPOTHESIZE:
+  → S_CLI_EXPLORE WHEN: CLI tools enabled AND hypotheses non-trivial    DO: A_FORM_HYPOTHESES
+  → S_TEST        WHEN: no CLI tools OR trivial hypotheses              DO: A_FORM_HYPOTHESES
+
+S_CLI_EXPLORE:
+  → S_TEST        DO: A_CLI_SUPPLEMENT (maestro delegate --role explore --mode analysis, run_in_background, STOP)
+
+S_TEST:
+  → S_REPORT      WHEN: hypothesis confirmed                  DO: A_TEST_HYPOTHESIS
+  → S_REPORT      WHEN: all hypotheses tested (some confirmed) DO: A_TEST_HYPOTHESIS
+  → S_ESCALATE    WHEN: max_hypotheses all failed              DO: A_TEST_HYPOTHESIS
+
+S_ESCALATE:
+  → S_HYPOTHESIZE WHEN: user broadens scope or provides new hypothesis   DO: ask_user
+  → S_REPORT      WHEN: user selects "Escalate" or still stuck          DO: mark INCONCLUSIVE
+
+S_REPORT:
+  → END           DO: A_SYNTHESIZE_REPORT
+
+</transitions>
+
+<actions>
+
+### A_FRAME_QUESTION
+
+1. Parse question, generate slug, create KNW-investigate-{slug}/
+2. Search prior knowledge: `maestro search "<question>"` + search .workflow/specs/learnings.md + read debug-notes.md
+3. Write initial understanding.md (question, prior knowledge summary, scope, timestamp)
+
+### A_COLLECT_EVIDENCE
+
+Parallel evidence gathering:
+1. Code search: Grep keywords from question
+2. File inspection: Read most relevant files
+3. Import tracing: follow dependency chain
+4. Git history: `git log --oneline -10 -- <relevant-files>`
+
+Each item → append evidence.ndjson: `{ts, type (code|git|search|doc), source (file:line), relevance (high|medium|low), content, note}`
+
+### A_FORM_HYPOTHESES
+
+Generate ranked hypotheses: each is specific, testable claim about "how/why".
+Rank by plausibility (evidence strength). Write to understanding.md:
+- `[HIGH]` hypothesis — Evidence: {refs}
+- `[MEDIUM]` hypothesis — Evidence: {refs}
+
+### A_CLI_SUPPLEMENT
+
+```
+maestro delegate "PURPOSE: Gather evidence for hypotheses
+TASK: Trace call chains and data flows per hypothesis | Find corroborating/contradicting patterns
+EXPECTED: JSON [{hypothesis_rank, evidence: [{file, line, supports: bool, explanation}]}]
+" --role explore --mode analysis
+```
+Run_in_background, STOP, wait. On callback: append to evidence.ndjson.
+
+### A_TEST_HYPOTHESIS
+
+For each hypothesis (rank order):
+1. Design test: what evidence would confirm/disprove?
+2. Execute: code trace, targeted search, data inspection
+3. Record: append evidence.ndjson with type: "test"
+4. Update: mark hypothesis confirmed / disproved / inconclusive
+
+### A_SYNTHESIZE_REPORT
+
+Write report.md: Answer (or INCONCLUSIVE), Evidence Trail table, Hypotheses Tested table, Key Learnings, Open Questions.
+Append to .workflow/specs/learnings.md: confirmed → roles="implement", disproved → roles="analyze" (gotcha).
+
+</actions>
+
+</state_machine>
+
+<error_codes>
+| Code | Condition | Recovery |
+|------|-----------|----------|
+| E002 | --scope path not found | Check path |
+| W002 | Very few evidence matches (<3) | Broaden search terms or expand scope |
+| W003 | All hypotheses inconclusive | Investigation marked INCONCLUSIVE |
+</error_codes>
+
+<success_criteria>
+- [ ] Evidence collected and logged to evidence.ndjson (structured NDJSON)
+- [ ] At least 1 hypothesis formed and tested
+- [ ] 3-strike escalation triggered if all fail
+- [ ] Report + spec-entry blocks written
+</success_criteria>
+
+<next_step_routing>
+- Save to specs → `/spec-add debug <finding>`
+- Follow code → `/learn-follow <path>`
+- Decompose patterns → `/learn-decompose <module>`
+</next_step_routing>