1.3 KiB
1.3 KiB
name, description
| name | description |
|---|---|
| work-item-definition | Use when a request is too vague to scope, estimate, or verify. Define the objective, scope, acceptance criteria, assumptions, dependencies, and only material open questions; do not implement it. |
Work Item Definition
Use when a request lacks enough detail to estimate or verify the intended technical outcome.
Workflow
- State the user or system outcome in concrete terms.
- Define what is in scope and what is explicitly out of scope based on the request and current behavior.
- Write observable acceptance criteria, including relevant failure or edge cases.
- Record constraints, dependencies, compatibility requirements, and assumptions separately. Before accepting external technology constraints as established, MUST apply the planning checkpoint in
technical-research; carry its evidence or unresolved gaps into the work item. - Ask only questions whose answers would materially change behavior, contracts, permissions, or acceptance. Choose safe reversible defaults for minor implementation details.
- Identify unresolved risks and a proportionate verification approach.
Return a bounded work item with objective, scope, criteria, assumptions, dependencies, and open questions. Do not invent business rules or start implementation unless asked.