diff --git a/.claude-plugin/marketplace.json b/.claude-plugin/marketplace.json index a1b7be9..de0fa74 100644 --- a/.claude-plugin/marketplace.json +++ b/.claude-plugin/marketplace.json @@ -12,7 +12,7 @@ { "name": "compound-engineering", "description": "AI-powered development tools that get smarter with every use. Make each unit of engineering work easier than the last. Includes 29 specialized agents, 22 commands, and 19 skills.", - "version": "2.34.0", + "version": "2.35.2", "author": { "name": "Kieran Klaassen", "url": "https://github.com/kieranklaassen", diff --git a/plugins/compound-engineering/.claude-plugin/plugin.json b/plugins/compound-engineering/.claude-plugin/plugin.json index 51a3d03..5bb71ad 100644 --- a/plugins/compound-engineering/.claude-plugin/plugin.json +++ b/plugins/compound-engineering/.claude-plugin/plugin.json @@ -1,6 +1,6 @@ { "name": "compound-engineering", - "version": "2.35.1", + "version": "2.35.2", "description": "AI-powered development tools. 29 agents, 22 commands, 19 skills, 1 MCP server for code review, research, design, and workflow automation.", "author": { "name": "Kieran Klaassen", diff --git a/plugins/compound-engineering/CHANGELOG.md b/plugins/compound-engineering/CHANGELOG.md index 731f70b..ede6b06 100644 --- a/plugins/compound-engineering/CHANGELOG.md +++ b/plugins/compound-engineering/CHANGELOG.md @@ -5,6 +5,14 @@ All notable changes to the compound-engineering plugin will be documented in thi The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). +## [2.35.2] - 2026-02-20 + +### Changed + +- **`/workflows:plan` brainstorm integration** — When plan finds a brainstorm document, it now heavily references it throughout. Added `origin:` frontmatter field to plan templates, brainstorm cross-check in final review, and "Sources" section at the bottom of all three plan templates (MINIMAL, MORE, A LOT). Brainstorm decisions are carried forward with explicit references (`see brainstorm: `) and a mandatory scan before finalizing ensures nothing is dropped. + +--- + ## [2.35.1] - 2026-02-18 ### Changed diff --git a/plugins/compound-engineering/commands/workflows/plan.md b/plugins/compound-engineering/commands/workflows/plan.md index 5cd43dc..9b1ab88 100644 --- a/plugins/compound-engineering/commands/workflows/plan.md +++ b/plugins/compound-engineering/commands/workflows/plan.md @@ -36,11 +36,19 @@ ls -la docs/brainstorms/*.md 2>/dev/null | head -10 - If multiple candidates match, use the most recent one **If a relevant brainstorm exists:** -1. Read the brainstorm document -2. Announce: "Found brainstorm from [date]: [topic]. Using as context for planning." -3. Extract key decisions, chosen approach, and open questions -4. **Skip the idea refinement questions below** - the brainstorm already answered WHAT to build -5. Use brainstorm decisions as input to the research phase +1. Read the brainstorm document **thoroughly** — every section matters +2. Announce: "Found brainstorm from [date]: [topic]. Using as foundation for planning." +3. Extract and carry forward **ALL** of the following into the plan: + - Key decisions and their rationale + - Chosen approach and why alternatives were rejected + - Constraints and requirements discovered during brainstorming + - Open questions (flag these for resolution during planning) + - Success criteria and scope boundaries + - Any specific technical choices or patterns discussed +4. **Skip the idea refinement questions below** — the brainstorm already answered WHAT to build +5. Use brainstorm content as the **primary input** to research and planning phases +6. **Critical: The brainstorm is the origin document.** Throughout the plan, reference specific decisions with `(see brainstorm: docs/brainstorms/)` when carrying forward conclusions. Do not paraphrase decisions in a way that loses their original context — link back to the source. +7. **Do not omit brainstorm content** — if the brainstorm discussed it, the plan must address it (even if briefly). Scan each brainstorm section before finalizing the plan to verify nothing was dropped. **If multiple brainstorms could match:** Use **AskUserQuestion tool** to ask which brainstorm to use, or whether to proceed without one. @@ -180,6 +188,7 @@ title: [Issue Title] type: [feat|fix|refactor] status: active date: YYYY-MM-DD +origin: docs/brainstorms/YYYY-MM-DD--brainstorm.md # if originated from brainstorm, otherwise omit --- # [Issue Title] @@ -207,8 +216,9 @@ class Test end ``` -## References +## Sources +- **Origin brainstorm:** [docs/brainstorms/YYYY-MM-DD--brainstorm.md](path) — include if plan originated from a brainstorm - Related issue: #[issue_number] - Documentation: [relevant_docs_url] ```` @@ -233,6 +243,7 @@ title: [Issue Title] type: [feat|fix|refactor] status: active date: YYYY-MM-DD +origin: docs/brainstorms/YYYY-MM-DD--brainstorm.md # if originated from brainstorm, otherwise omit --- # [Issue Title] @@ -277,8 +288,9 @@ date: YYYY-MM-DD [What could block or complicate this] -## References & Research +## Sources & References +- **Origin brainstorm:** [docs/brainstorms/YYYY-MM-DD--brainstorm.md](path) — include if plan originated from a brainstorm - Similar implementations: [file_path:line_number] - Best practices: [documentation_url] - Related PRs: #[pr_number] @@ -306,6 +318,7 @@ title: [Issue Title] type: [feat|fix|refactor] status: active date: YYYY-MM-DD +origin: docs/brainstorms/YYYY-MM-DD--brainstorm.md # if originated from brainstorm, otherwise omit --- # [Issue Title] @@ -416,7 +429,11 @@ date: YYYY-MM-DD [What docs need updating] -## References & Research +## Sources & References + +### Origin + +- **Brainstorm document:** [docs/brainstorms/YYYY-MM-DD--brainstorm.md](path) — include if plan originated from a brainstorm. Key decisions carried forward: [list 2-3 major decisions from brainstorm] ### Internal References @@ -495,6 +512,16 @@ end ### 6. Final Review & Submission +**Brainstorm cross-check (if plan originated from a brainstorm):** + +Before finalizing, re-read the brainstorm document and verify: +- [ ] Every key decision from the brainstorm is reflected in the plan +- [ ] The chosen approach matches what was decided in the brainstorm +- [ ] Constraints and requirements from the brainstorm are captured in acceptance criteria +- [ ] Open questions from the brainstorm are either resolved or flagged +- [ ] The `origin:` frontmatter field points to the brainstorm file +- [ ] The Sources section includes the brainstorm with a summary of carried-forward decisions + **Pre-submission Checklist:** - [ ] Title is searchable and descriptive