Clarify fuzzy requirements and produce a draft handoff summary.
npx skills add https://github.com/MoonCoder-HAPPY/SpecDo --skill specdo-brainstorming
Please help me install this Agent Skill. Skill: specdo-brainstorming Source: https://github.com/MoonCoder-HAPPY/SpecDo/tree/main/specdo-brainstorming Command: npx skills add https://github.com/MoonCoder-HAPPY/SpecDo --skill specdo-brainstorming
Clarify fuzzy requirements before repository analysis and artifact creation to stabilize scope, acceptance criteria, constraints, and product intent for the SpecDo lifecycle.
Ask clarifying questions and prepare a draft handoff summary for user confirmation.
High-intent search queries and answers about installing and using this skill.
To clarify fuzzy requirements before repository analysis, use a structured, question-driven approach to articulate target behavior, scope boundaries, constraints, and acceptance signals. This stabilizes product intent and ensures safe handoffs to downstream planning steps.
The best way to stabilize scope and acceptance criteria is through a structured brainstorming process that guides stakeholders to articulate product intent. This produces a draft handoff summary after explicit user confirmation to gate readiness.
To prepare a requirements handoff summary, guide stakeholders through clarifying questions targeting scope and constraints. After explicit user confirmation, a draft handoff summary is produced for the next skill in the lifecycle, such as explore or create_change.
Yes, contract-driven handoff requires gated readiness checks to ensure safe transitions to downstream artifacts. This approach encapsulates governance and handoff contracts to verify scope, constraints, and acceptance criteria before proceeding.
Yes, structured brainstorming defines constraints and product intent before writing a proposal. It leverages reference guidance for brainstorming methods to gate readiness and enable safe handoffs to downstream planning steps.
OzeroHAXDefine project context, problem statement, and MVP boundaries.
pabloimrik17Guide users through a complete OpenSpec workflow cycle in their codebase.
rock-huVerify OpenSpec change implementations against specs, tasks, and design artifacts.
lpjhelderCreate testable work plans with acceptance criteria and execution handoffs.
