Putting it together

Let's take a real case: a stakeholder sends you a vague email with a new request. See how the 9 prior modules connect into a single workflow.

The scenario

Step 1: Clarify with AI before asking the stakeholder

Use ChatGPT/Claude. Paste the email, ask:

# Rol
Ești un Senior BA. Ai un stakeholder care a trimis un request vag.

# Task
Generează 5 întrebări de clarificare prioritizate, plus o ipoteză
de bază pe care o pot confirma rapid (ca să nu blocăm dezvoltarea
dacă răspunsurile întârzie).

# Context
[lipești emailul]

# Format
- Întrebări numerotate, de la cea mai importantă
- O ipoteză de bază clar marcată
- Limba română

In 30 seconds you have 5 good questions and a starter hypothesis. Module 2 (prompt anatomy) gave you the structure.

Step 2: User stories with assisted drafting

Stakeholder replies: "Excel, monthly, Finance managers only, no sensitive data". Now you ask AI to turn the answer into Gherkin user stories (Module 2). Then you review manually — never copy-paste without reading.

Step 3: Check existing code with Copilot

Open VS Code. In Copilot Chat (Module 7) ask: "Is there already an Excel export in this project? Where?". Copilot searches and gives you relevant files. Now you know if you're reusing or building from scratch.

Step 4: Edit specs in a branch

Module 8 helps here. You do git checkout -b andrei/finance-export-specs, edit /docs/specs/finance-export.md, commit, push, open a PR. Reviewer: tech lead.

Step 5: Launch a sub-agent to check impact

In Claude Code (Module 9): "Launch an Explore agent to tell me what other features depend on the report generation module". The sub-agent searches 100+ files, returns a short report with 3 dependencies.

Step 6: Update PR with impact analysis

Add an "Impact" section to the PR description with the results. Tech lead approves. Devs start work with clear specs, eliminated questions, identified dependencies.

Golden rules

• AI accelerates — it doesn't replace judgment. Verify everything.
• Document the why, not just the what. Specs with "why" survive over time.
• Branch + PR for any change > a single line. Audit + collaboration.
• Sub-agents for research, prompts for output, tools for actions. Use the right tool.