Requirement Convergence
Separates the outcome a change must produce from the requirements proposed to reach it...
Install
npx skills add shinpr/claude-code-workflows --skill requirement-convergence -g -a claude-code -y- Repository
- shinpr/claude-code-workflows708
- Category
- Design
- Updated
- 7d ago
- License
- MIT
- Context cost
- Lightabout 1,467 tokens
- Runs scripts
- No, instructions only
What it does
Separates the outcome a change must produce from the requirements proposed to reach it, records what the user excluded, and bands cost from decision-relevant repository evidence. Use when a requirement enters a workflow, before design begins.
Requirement Convergence
Purpose
Requirements arrive bloated, ambiguous, or aimed at the wrong outcome. A capable model reconciles all three into a coherent plan and builds it faithfully, delivering exactly what was asked for when what was asked for was wrong.
This skill converges what to build. How to build it, and which documents the change requires, are settled after the what is.
Convergence Fields
| Field | Pass condition |
|---|---|
outcome | One observable result. A requirement that does not serve it is excess. |
requirements[] | Every build-relevant item labeled current-state or desired-future. |
nonGoals[] | Authored by the user, or the user stated there are none. |
cost | A band with the repository and lifecycle evidence that places it, plus the unknowns that remain. |
cost is a rough band, not the effort estimate a work plan schedules against; requirements cannot support person-days. Its unknowns carry more decision weight than its size.
Classify from the user's own retained wording, not from an analyzer's restatement of it: wording that asks for an evaluation, describes a speculative idea, or suggests a mechanism stays in active convergence context as a judgment-only candidate. requirements[] and durable documents receive a candidate only after explicit user confirmation.
Each field carries a readiness label: ready, weak, or weak-but-explicit (weak, and the user agreed to leave it unresolved). Only the user sets weak-but-explicit. Requirements are converged when every applicable field is ready or weak-but-explicit.
Judgment rules per field: references/criteria.md.
Hearing Protocol
Run the hearing after scope analysis has produced the facts needed to judge the convergence fields. The workflow using this skill owns the interaction method and routing; this skill defines the hearing content and pass conditions.
