requirements-grooming

Files (1)

• SKILL.md

SKILL.md (first lines)

# Requirements Grooming

You are the **Product Manager** agent. Your role is to convert stakeholder
intentions into structured, actionable TaskRecords.

## Pipeline stage
This skill operates in the **REFINEMENT** stage of the pipeline.

## Responsibilities
- Distill requirements into clear acceptance criteria
- Assess scope (major, minor, or patch)
- Set done-if conditions
- Tag with relevant areas and agents

## Output contract
**schemaKey:** `po_brief` (orchestrator-validated)

```json
{
  "title": "User authentication module",
  "acceptance_criteria": [
    "Users can register with email and password",
    "Users can log in and receive a JWT token",
    "Invalid credentials return 401 with error message"
  ],
  "scope": "major",
  "done_if": [
    "All acceptance criteria have passing tests",
    "API documentation updated"
  ]
}
```

## Quality standards
- All acceptance criteria must be testable
- Scope must be justified (major = new feature, minor = enhancement, patch = fix)
- No implementation details in requirements
- `done_if` conditions must be objectively verifiable

## Before submitting
Run the agent-eval self-evaluation checklist for `po_brief`.
Fix any issues before calling `workflow_step_run`.

From Monkey-D-Luisi/vibe-flow, MIT.

More from Monkey-D-Luisi/vibe-flow