From greymatter
Assesses a captured brainstorm and decides whether it becomes a single spec or a multi-spec roadmap, then hands off to the appropriate writing skill.
How this skill is triggered — by the user, by Claude, or both
Slash command
/greymatter:assessing-brainstormsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Decide whether a brainstorm becomes one spec or a roadmap of several, then hand off to the matching skill. The verb is `assess` because the work *is* the assessment — single shippable unit, or multiple? — not a `git fork`-style copy.
Decide whether a brainstorm becomes one spec or a roadmap of several, then hand off to the matching skill. The verb is assess because the work is the assessment — single shippable unit, or multiple? — not a git fork-style copy.
| Signal | Spec | Roadmap |
|---|---|---|
| Single coherent feature with one clear shipping definition | ✓ | |
| Two or more independent shippable units that share a thesis | ✓ | |
| Decision table fits in one screen, open threads < 5 | ✓ | |
| Brainstorm body > ~300 lines or multiple §2 decision tables | ✓ | |
| The user already used the word "arc," "phases," or "tracks" | ✓ |
If two or more roadmap signals fire, recommend roadmap. Otherwise recommend spec. Lead with the recommendation; let the user override.
Read the brainstorm. Frontmatter, §2 decision table, open threads, next steps. Confirm it's complete (no TBDs in §2, open threads triaged into "blocking" vs "shape-only").
State the call. "Reading this as a [spec | roadmap] because [signals]. Disagree?" Wait for confirmation.
Invoke the verb:
node greymatter/scripts/dev-pipeline.js assess <brainstorm-path> --to spec|roadmap
The verb copies the canonical templates next to the brainstorm and patches frontmatter with the brainstorm topic. (Brainstorms are scaffolded by dev-pipeline.js init as brainstorm.md — no temp. rename needed.)
Hand off:
writing-specs. Tell it the brainstorm path. Stop.writing-roadmaps. Tell it the brainstorm path. Stop.You do not draft the spec or roadmap yourself. This skill ends at the handoff.
TBDs, send the user back to brainstorming to close them. Assessing prematurely surfaces churn downstream.npx claudepluginhub advenire-consulting/greymatter --plugin greymatterDrafts a specification from a brainstorm or roadmap row, producing a contract of what will and won't be built. Useful when transitioning from ideation to planning.
Facilitates design exploration and spec creation for new features. Enforces design-before-implementation with structured phases: context gathering, argumentation, and spec output.
Refines rough ideas into executable specifications via collaborative questioning, alternative exploration, and incremental validation. Invoke before creative work or implementation.