Gate code and project commands until a written design spec is approved.
npx skills add https://github.com/lucasmccomb/ccgm --skill brainstorm-lucasmccomb
Please help me install this Agent Skill. Skill: brainstorm Source: https://github.com/lucasmccomb/ccgm/tree/main/modules/brainstorm/skills/brainstorm Command: npx skills add https://github.com/lucasmccomb/ccgm --skill brainstorm-lucasmccomb
Prevents premature implementation by enforcing a written, reviewed design specification before any code, scaffolding, or project-modifying commands are produced. This reduces rework, hidden tradeoffs, and architecture drift by making design decisions explicit and approved before implementation begins.
Ask the assistant to "Design a spec for adding a rate limiter to the API gateway and draft the approved design in docs/brainstorm-notes/".
High-intent search queries and answers about installing and using this skill.
Enforce a design-first workflow by using a hard gate that refuses to produce code, scaffolding, or project-modifying commands until a written design spec is explicitly approved. This prevents premature implementation and reduces rework.
A design spec is a written document outlining proposed approaches with tradeoffs for architecture changes. You need a formal spec for migrations, such as migrating auth systems, to make design decisions explicit and traceable before implementation begins.
Write a spec by guiding through context exploration, proposing 2-3 distinct approaches with tradeoffs, and recording the spec in a dated session directory. Perform a self-review to ensure decisions and open questions are traceable.
Scaffolding project files is blocked by the hard gate enforcement. No pseudocode, scaffolding, or modifying commands are produced until a written design spec exists in docs/brainstorm-notes/ and is explicitly approved.
Document architecture decisions by creating dated session directories and session.md logs within docs/brainstorm-notes/. This audit-friendly artifact ensures tradeoff analysis and traceable decisions are recorded before handing off to planning.
Your assistant refuses to generate code because a design-first gate is active, requiring an approved written design spec before any implementation. This prevents hidden tradeoffs and architecture drift by making design decisions explicit.
dtsongTransform natural language project descriptions into structured engagement briefs.
korwlik23Turns rough ideas into approved implementation plans before code is written.
espensevSynchronize architecture docs and code-facing guides with source changes.
LerianStudioAutomate development completion validation with acceptance criteria checks and explicit user approval.
