---
name: project-drivers
description: Document business drivers with requirement traceability
argument-hint: "[\"revision description\" | --category=strategic|operational|compliance|technology]"
---

<objective>
Document business drivers that justify the project and trace to requirements.

Creates the business case with value quantification and driver-to-requirement linkage.

**Creates:**
- `docs/project/business-drivers.md` — Business drivers with value metrics and traceability

**Prerequisites:** Recommended to have project state and stakeholders first.

**After this command:** Run `/pact-project-requirements` to define detailed requirements with traceability.
</objective>

<execution_context>
@references/workflows/project-drivers.md
@references/templates/project/business-drivers.md
@references/gate-protocol.md
@references/revision-protocol.md
@references/conversational-gathering.md
</execution_context>

<context>
Input: $ARGUMENTS
Project State: docs/project-state.md (if exists)
Principles: docs/project/principles.md (if exists)
Stakeholders: docs/project/stakeholders.md (if exists)
Output: docs/project/business-drivers.md
</context>

<when_to_use>
**Use this command for:**
- Projects requiring business justification
- Projects with investment/budget decisions
- Creating traceability from business value to work

**Skip this command if:**
- Internally-driven technical work with no business case needed
- Compliance-only projects (use risks command instead)
</when_to_use>

<process>
1. Load project context
2. Detect existing document — if exists, offer: Revise | Recreate | View | Cancel
3. If revising: gather changes, apply with Edit tool, bump version, update history
4. If creating: identify drivers by category, gather value details, set up traceability
5. Scan downstream impact (requirements.md)
6. Validate and report
</process>

<success_criteria>
- [ ] Existing document detected and user chose action (if applicable)
- [ ] Business drivers identified and categorized
- [ ] Value documented (quantified where possible)
- [ ] Traceability framework established
- [ ] Document written to docs/project/business-drivers.md
- [ ] Version and revision history updated (if revising)
- [ ] Downstream impact reported (if revising)
- [ ] Document passes markdownlint
</success_criteria>