maestro-flow 0.5.35 → 0.5.37

package/.codex/skills/domain-add/SKILL.md

@@ -0,0 +1,79 @@
+---
+name: domain-add
+description: Register a domain term into project glossary
+argument-hint: "<canonical> <definition>"
+allowed-tools: Read, Write, Bash, Glob, Grep
+---
+
+<purpose>
+Register a domain term into `.workflow/domain/glossary.yaml`. Domain terms are automatically injected into agent context via hooks (domain-compact for all prompts, domain-expanded on keyword match).
+
+```bash
+$domain-add "auth-token" "Short-lived credential for API authentication"
+$domain-add "event-bus" "Central pub-sub message broker for cross-module communication"
+```
+
+**CLI alternative**: `maestro domain add "<canonical>" "<definition>" --tier core|extended|peripheral`. Used by finish-work for programmatic domain term extraction from session outputs.
+</purpose>
+
+<context>
+$ARGUMENTS — `<canonical> <definition>` where canonical is a kebab-case term name.
+
+**Prerequisites**: `.workflow/domain/` must exist (run `maestro domain init` if missing).
+
+**Domain term lifecycle**: discover/manual → register → active → (optional) deprecated → removed
+</context>
+
+<execution>
+
+### Step 1: Parse Input
+
+Extract canonical (first token, kebab-case) and definition (remainder) from arguments.
+- Validate canonical is non-empty, kebab-case (lowercase, hyphens only)
+- Validate definition is non-empty, ≤200 chars (E001 if missing)
+
+### Step 2: Validate Domain Directory
+
+Verify `.workflow/domain/glossary.yaml` exists (E002). If not, run `maestro domain init`.
+
+### Step 3: Check Duplicates
+
+Read existing glossary and check for:
+- Exact duplicate (same canonical name) → report existing entry, exit
+- Near match (Levenshtein ≤ 2 or alias overlap) → warn, ask to confirm or merge
+
+### Step 4: Extract Metadata
+
+Auto-derive from the definition and codebase context:
+- **aliases** (1-3): common abbreviations, Chinese translations, alternate forms
+- **keywords** (3-5): search terms for discovery
+- **tier**: `core` | `extended` | `peripheral`
+- **relationships**: scan existing glossary for related terms
+
+### Step 5: Register Term
+
+```bash
+maestro domain add "<canonical>" "<definition>" --tier <tier>
+maestro domain update "<canonical>" --aliases "alias1,alias2" --keywords "kw1,kw2" --relationships "rel1,rel2"
+```
+
+### Step 6: Confirm
+
+Display: canonical name, definition, aliases, tier, relationships, and verify command `maestro domain list`.
+</execution>
+
+<error_codes>
+| Code | Severity | Description |
+|------|----------|-------------|
+| E001 | fatal | Canonical name and definition are both required |
+| E002 | fatal | `.workflow/domain/` not initialized — run `maestro domain init` first |
+| E003 | fatal | Term already registered with same canonical name |
+</error_codes>
+
+<success_criteria>
+- [ ] Canonical name and definition parsed and validated
+- [ ] No duplicate term in glossary
+- [ ] Aliases and keywords auto-extracted
+- [ ] Term written to glossary.yaml with tier and relationships
+- [ ] Confirmation displayed with verify command
+</success_criteria>

package/.codex/skills/domain-discover/SKILL.md

@@ -0,0 +1,43 @@
+---
+name: domain-discover
+description: Discover domain term candidates from codebase
+argument-hint: "[--auto]"
+allowed-tools: Read, Bash, Glob, Grep
+---
+
+<purpose>
+Scan codebase for potential domain terms not yet in `.workflow/domain/glossary.yaml`. Presents candidates with confidence scores for interactive registration.
+
+`--auto`: auto-register candidates with confidence ≥ 0.8 without prompting.
+</purpose>
+
+<execution>
+
+### Step 1: Scan Codebase
+
+Run `maestro domain discover` to scan TypeScript interfaces, types, enums, const patterns, API routes, and README headings.
+
+### Step 2: Filter Existing
+
+Remove candidates already registered in glossary.yaml (by canonical name or alias match).
+
+### Step 3: Present Candidates
+
+Display ranked candidates with confidence scores:
+
+```
+=== DOMAIN TERM CANDIDATES ({N} found) ===
+
+  0.92  session-context — Runtime state container for active workflow session
+  0.85  skill-resolver — Module that maps skill names to SKILL.md file paths
+  0.71  chain-graph — DAG definition for multi-step command sequences
+  ...
+
+Register? (all | select by number | skip)
+```
+
+### Step 4: Register Selected
+
+For each confirmed candidate, run `maestro domain add "<canonical>" "<definition>"`.
+
+</execution>

package/.codex/skills/domain-list/SKILL.md

@@ -0,0 +1,38 @@
+---
+name: domain-list
+description: List registered domain terms from glossary
+argument-hint: "[--tier core|extended|peripheral]"
+allowed-tools: Read, Bash, Glob, Grep
+---
+
+<purpose>
+List all registered domain terms from `.workflow/domain/glossary.yaml`. Shows canonical name, definition, tier, aliases, and status.
+</purpose>
+
+<execution>
+
+### Step 1: Load Glossary
+
+Read `.workflow/domain/glossary.yaml`. If not exists, report "No domain glossary — run `maestro domain init`".
+
+### Step 2: Filter and Display
+
+Apply optional `--tier` filter. Display terms grouped by tier (core → extended → peripheral):
+
+```
+=== DOMAIN TERMS ({N} total) ===
+
+[core]
+  auth-token — Short-lived credential for API authentication
+    aliases: 令牌, access-token | keywords: auth, credential, jwt
+  event-bus — Central pub-sub message broker
+    aliases: 事件总线 | keywords: pubsub, messaging
+
+[extended]
+  ...
+
+[deprecated]
+  wikiindexer → search-engine (successor)
+```
+
+</execution>

package/.codex/skills/learn-decompose/SKILL.md

@@ -50,7 +50,7 @@ $ARGUMENTS — target path/module and optional flags.
 Parse flags from `$ARGUMENTS`: `-y`/`--yes`, `--patterns <list>`, `--save-spec`, `--save-wiki`, `--continue`, `-c N`.
 Extract remaining text as target path/module.
 
-Resolve target to file list. Load coding specs: `maestro spec load --category coding` for documented patterns and conventions. Load existing patterns from `coding-conventions.md` + `.workflow/specs/learnings.md` for dedup set. Browse wiki: `maestro search --category coding`, load relevant entries.
+Resolve target to file list. Load coding specs: `maestro load --type spec --category coding` for documented patterns and conventions. Load existing patterns from `coding-conventions.md` + `.workflow/specs/learnings.md` for dedup set. Browse wiki: `maestro search --category coding`, load relevant entries.
 
 ### Phase 2: Wave 1 — Parallel Dimension Scans
 

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

@@ -9,9 +9,6 @@ allowed-tools: Read, Write, Edit, Bash, Glob, Grep, request_user_input
 Guided reading experience for code files, wiki entries, or topics. Walks through content
 section by section using 4 forcing questions to extract patterns, identify assumptions,
 and build a structured understanding map. Insights persist to `.workflow/specs/learnings.md`.
-
-Unlike `learn-decompose` which is parallel pattern extraction, this is sequential
-deep reading that builds understanding incrementally.
 </purpose>
 
 <context>

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

@@ -9,9 +9,6 @@ allowed-tools: Read, Write, Edit, Bash, Glob, Grep, request_user_input
 Systematic investigation for understanding questions (not bug-fixing). 4-phase approach
 with scope lock and 3-strike escalation. Produces structured evidence trails and
 understanding documents that persist to the learning system.
-
-Unlike `quality-debug` (fixing bugs during execution), this answers "how does X work?",
-"why does Y happen?", "what would happen if Z?" questions.
 </purpose>
 
 <context>
@@ -28,7 +25,7 @@ $ARGUMENTS — question text and optional flags.
 
 ### Stage 1: Frame the Question
 - Parse question, generate slug, create investigation directory
-- Load debug specs: `maestro spec load --category debug` for known issues and patterns
+- Load debug specs: `maestro load --type spec --category debug` for known issues and patterns
 - Search prior knowledge: `maestro search --category debug`, wiki search, grep .workflow/specs/learnings.md
 - Write initial `understanding.md`
 

package/.codex/skills/learn-retro/SKILL.md

@@ -10,8 +10,6 @@ Unified retrospective combining git activity analysis and decision quality evalu
 Two lenses, usable independently or together:
 - **git**: Commit metrics, session detection, per-author breakdown, file hotspots, trends
 - **decision**: Decision tracing across wiki/specs/git, multi-perspective evaluation via 3 parallel agents
-
-Works on raw git history and wiki/spec data — does not require completed phase artifacts.
 </purpose>
 
 <context>