Collect project decisions across three modes and output a handoff to /spec.
npx skills add https://github.com/anhtrinh919/claude-code-sdd --skill ba-anhtrinh919
Please help me install this Agent Skill. Skill: ba Source: https://github.com/anhtrinh919/claude-code-sdd/tree/main/skills/ba Command: npx skills add https://github.com/anhtrinh919/claude-code-sdd --skill ba-anhtrinh919
Business Analyst mode — drills the user to collect all decisions needed to drive the SDD build system. Three modes detected from context: (1) new project (no mission.md) — demand validation, constitution grill, master user flow; (2) start phase (mission.md exists) — phase scope, user stories, screen inventory, competitor patterns; (3) between phases — lightweight replan. Outputs a decisions handoff to /spec. Trigger on: /ba, or when /build reaches the BA step.
Say "/ba" to start decision collection for your project.
High-intent search queries and answers about installing and using this skill.
To collect decisions for spec-driven development, trigger a structured interview process that validates demand, defines the project constitution, and maps the master user journey. This captures all mission, tech stack, and roadmap artifacts for handoff.
Spec-driven development decision tracking is the process of recording mission, tech stack, and roadmap choices through structured interviews. You need it when starting a new project, scoping a new phase, or replanning between phases to ensure builds are driven by validated decisions.
Scoping a new phase using business analysis involves detecting an existing mission context, then collecting phase-specific scope, user stories, screen inventory, and competitor patterns. This outputs a targeted decisions handoff to drive the next build stage.
Yes, you can use structured interviews to generate a master user journey. The business analysis process drills down through demand validation and constitutional rules to extract and map the complete master user flow for new project handoffs.
You do not need a mission file to start business analysis decision collection. The system detects the context mode: without a mission file it starts a new project, and with an existing mission file it transitions to phase scoping or lightweight replanning.
SakshamKandelAnalyze project retrospectives to surface velocity, blockers, and improvement patterns.
ParetofilmVerify artifact-specific pitfalls across PRDs, specs, plans, and code.
Adelie-SquadGenerate interview plans and analysis artifacts from qualitative research inputs.
OpenWaggleAnalyzes code repositories to generate structured project requirement documents.
