What problem does it solve?
After an ideation session ends with a decision, teams often jump straight into requirements or specs with too much detail or too little context. This Skill bridges that gap by converting the ideation decision into a minimal pre-spec package, with explicit open questions, so the next pipeline starts with exactly what it needs and nothing more.
Core Features & Use Cases
- Minimal Scope Definition: Derives the smallest valuable first delivery slice from the session's decision and risk files, without writing requirements, data models, or architecture.
- Explicit Doubt Tracking: Marks every unresolved point as
[DÚVIDA] in a format consumable by the clarify step, instead of inventing answers.
- Pipeline Routing: Resolves the correct next command based on project context, routing legacy projects to requirements gathering and greenfield projects to new-project ideation.
- Use Case: After a brainstorm and arbitration session decides to build a notification module for a legacy system, run this Skill to produce a
pre-spec.md capturing the problem, chosen path, minimum scope, non-goals, constraints, and open questions, then hand it off to the requirements pipeline.
Quick Start
Ask the agent to generate the pre-spec for the current ideation session after the decision file has been created by the arbiter step.
