Guide structured Q&A to document decisions and generate a _step1_decisions.md artifact.
npx skills add https://github.com/gsa9/3-step-plan-claude-code --skill step1
Please help me install this Agent Skill. Skill: step1 Source: https://github.com/gsa9/3-step-plan-claude-code/tree/main/skills/step1 Command: npx skills add https://github.com/gsa9/3-step-plan-claude-code --skill step1
This Skill guides users through a structured decision-making process to define project requirements and scope before execution, ensuring clarity and alignment.
_step1_decisions.md file to bridge the gap between decision-making and planning./step1 to clarify requirements, choose between different technical approaches, and document potential risks before writing any code.Initiate the decision-making process by typing /step1.
High-intent search queries and answers about installing and using this skill.
To gather requirements and scope a software project, use a structured decision-making Q&A process that identifies decision points, challenges assumptions, and documents rationale to ensure clarity before execution.
The best way to document technical decisions is through an iterative process that tracks choices, rationale, rejected alternatives, and risks, culminating in a markdown artifact for subsequent planning stages.
Yes, you can use a structured Q&A approach to engage stakeholders, refine decisions through one-on-one interaction, and achieve project scope alignment by explicitly documenting choices and identified risks.
You start the decision-making process for a new software feature by initiating a guided iterative dialogue that explores requirements, chooses between technical approaches, and clarifies potential risks.
The decision tracking output uses a markdown file format named `_step1_decisions.md`, which bridges the gap between decision-making and execution by capturing all documented choices and risks.
You should not use a structured decision-making process when immediate execution is required without scope definition, as this approach deliberately pauses development to challenge assumptions and document risks first.
vinvcnRefine raw product ideas into structured concepts with MVP scope.
kardelitaituStructure tasks, estimates, and roadmaps for project planning workflows.
NagyViktTransform abstract project ideas into validated design specifications through iterative dialogue.
khgs2411Automates architectural decision documentation in PLAN.md during brainstorming sessions.