← ClaudeAtlas

superpowersbrainstorminglisted

Use during devflow TASK-01 requirement clarification before design or implementation. Explores user intent, requirements, constraints, and success criteria.
Tencent/LoopForge · ★ 1,220 · AI & Automation · score 82
Install: claude install-skill Tencent/LoopForge
# Brainstorming Ideas Into Designs Help turn ideas into fully formed designs and specs through natural collaborative dialogue. ## DevFlow Override When this skill is invoked by `$devflow-codex` for TASK-01 requirement clarification: - Save the clarified requirement report to `{artifacts_dir}/01-requirement/requirement-report.md`. - Do not save to `docs/superpowers/specs/` unless the user explicitly asks for a standalone superpowers spec. - Do not commit the requirement report. - Do not invoke `writing-plans`; TASK-02 architect writes `02-design/tech-design.md` and `02-design/execution-plan.md`. - The report must include: AI codebase/context analysis, clarification Q&A, accepted scope, excluded scope, success criteria, risks, and open questions. - After the report is written and the user has approved the clarified requirement, update `workflow-state.json` with `TASK-01_completed` and route to architect. - In devflow mode, medium/large TASK-01 must not be completed automatically. Even when the initial request appears complete, ask the user to confirm the clarified scope, success criteria, and exclusions before writing `TASK-01_completed`. - Do not use "no additional clarification needed" as a reason to skip user confirmation. If there is no obvious ambiguity, ask a confirmation question instead of continuing automatically. - In devflow mode, this override supersedes the default sections below that require writing to `docs/superpowers/specs/`, committing, running t