maestro-flow 0.5.0 → 0.5.1

package/workflows/knowhow.md

@@ -93,7 +93,7 @@ Capture reusable knowledge into `.workflow/knowhow/`.
 
 ### Step 2: Generate Content by Type
 
-#### session (KNW-{YYYYMMDD}-{HHMM}.md)
+#### session (KNW-{YYYYMMDD}-{slug}.md)
 
 Extract from current conversation. Sections:
 
@@ -115,13 +115,14 @@ Extract from current conversation. Sections:
 Plan detection priority: IMPL_PLAN.md > TodoWrite > user-stated > inferred.
 Rules: VERBATIM plan, ABSOLUTE paths, decisions include reasoning.
 
-#### template (TPL-{YYYYMMDD}-{HHMM}.md)
+#### template (TPL-{YYYYMMDD}-{slug}.md)
 
 Reusable code or configuration pattern. Sections:
 
 ```markdown
 ---
 title: {descriptive name}
+description: {one-line summary for search results}
 type: template
 lang: {typescript|python|bash|yaml|...}
 tags: [{comma-separated}]
@@ -157,13 +158,14 @@ Additional context.
 - `Code` — The actual template, ready to copy
 - `Dependencies` — What's needed before using
 
-#### recipe (RCP-{YYYYMMDD}-{HHMM}.md)
+#### recipe (RCP-{YYYYMMDD}-{slug}.md)
 
 Step-by-step operational guide. Sections:
 
 ```markdown
 ---
 title: {goal summary}
+description: {one-line summary for search results}
 type: recipe
 tags: [{comma-separated}]
 created: {ISO timestamp}
@@ -201,13 +203,14 @@ What success looks like.
 - `Expected Outcome` — Measurable result
 - `Common Pitfalls` — Known gotchas from experience
 
-#### reference (REF-{YYYYMMDD}-{HHMM}.md)
+#### reference (REF-{YYYYMMDD}-{slug}.md)
 
 External documentation digest. Sections:
 
 ```markdown
 ---
 title: {reference title}
+description: {one-line summary for search results}
 type: reference
 source: {original URL}
 tags: [{comma-separated}]
@@ -243,13 +246,14 @@ Additional context.
 - `Quick Examples` — Most-used snippets first
 - `last_verified` — When the source was last checked
 
-#### decision (DCS-{YYYYMMDD}-{HHMM}.md)
+#### decision (DCS-{YYYYMMDD}-{slug}.md)
 
 Architecture Decision Record. Sections:
 
 ```markdown
 ---
 title: {decision summary}
+description: {one-line summary for search results}
 type: decision
 status: {proposed|accepted|superseded}
 tags: [{comma-separated}]
@@ -292,13 +296,14 @@ Why this choice over alternatives.
 - `Rationale` — The "why" matters more than the "what"
 - `Consequences` — Both positive and negative; be honest about trade-offs
 
-#### tip (TIP-{YYYYMMDD}-{HHMM}.md)
+#### tip (TIP-{YYYYMMDD}-{slug}.md)
 
 Quick note. Minimal structure:
 
 ```markdown
 ---
 title: {tip summary}
+description: {one-line summary for search results}
 type: tip
 tags: [{comma-separated}]
 created: {ISO timestamp}
@@ -328,13 +333,14 @@ Tag quality rules:
 
 ### Step 4: Write File
 
-Write to `.workflow/knowhow/{PREFIX}-{YYYYMMDD}-{HHMM}.md`.
+Write to `.workflow/knowhow/{PREFIX}-{YYYYMMDD}-{slug}.md`.
 
 Frontmatter keys by type:
 
 | Field | session | template | recipe | reference | decision | tip |
 |-------|:-------:|:--------:|:------:|:---------:|:--------:|:---:|
 | title | Y | Y | Y | Y | Y | Y |
+| description | Y | Y | Y | Y | Y | Y |
 | type | Y | Y | Y | Y | Y | Y |
 | tags | Y | Y | Y | Y | Y | Y |
 | created | Y | Y | Y | Y | Y | Y |
@@ -367,7 +373,7 @@ maestro wiki list --type knowhow --role plan  # decisions only
 
 ```
 store_knowhow { operation: "search", query: "deploy" }
-store_knowhow { operation: "add", type: "template", title: "...", body: "..." }
+store_knowhow { operation: "add", type: "template", title: "...", description: "...", body: "..." }
 ```
 
 ### Type Label Reference

package/workflows/specs-add.md

@@ -97,7 +97,7 @@ Keyword quality rules:
 ```
 Entry format (closed-tag), date = YYYY-MM-DD, title = first meaningful phrase:
 
-<spec-entry category="{category}" keywords="{kw1},{kw2},{kw3}" date="{YYYY-MM-DD}">
+<spec-entry category="{category}" keywords="{kw1},{kw2},{kw3}" date="{YYYY-MM-DD}" title="{title}" description="{one-line summary}">
 ### {title}
 {content}
 </spec-entry>

package/workflows/specs-setup.md

@@ -228,9 +228,9 @@ Schema: matches `recipe` type defined in `~/.maestro/workflows/knowhow.md` Part
 
 **Skip rule:** If signals are missing, skip the recipe — do NOT generate placeholders.
 
-**Idempotency rule:** Before writing, glob `.workflow/knowhow/RCP-*-{slug}.md`. If a file matching the slug exists, do NOT overwrite — write `.workflow/knowhow/RCP-{YYYYMMDD-HHMM}-{slug}.proposed.md` instead and mention it in Step 7 summary so the user can diff and merge manually.
+**Idempotency rule:** Before writing, glob `.workflow/knowhow/RCP-*-{slug}.md`. If a file matching the slug exists, do NOT overwrite — write `.workflow/knowhow/RCP-{YYYYMMDD}-{slug}.proposed.md` instead and mention it in Step 7 summary so the user can diff and merge manually.
 
-**Filename:** `.workflow/knowhow/RCP-{YYYYMMDD-HHMM}-{slug}.md` (timestamp aligns with rest of knowhow store, slug disambiguates).
+**Filename:** `.workflow/knowhow/RCP-{YYYYMMDD}-{slug}.md` (date + semantic slug for readability).
 
 **Tags rule:** Match content language (English codebase → English tags). Always include `workflow`, the slug, and the detected framework (e.g. `vitest`, `pytest`). Add `auto-generated` so users can identify spec-setup output for later pruning.