Separates the outcome a change must produce from the requirements proposed to reach it, records what the user excluded, and bands cost from structure. Use when a requirement enters a workflow, before design begins, or when "how far do we go/what's out of scope/is this worth it" is mentioned.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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 structural 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.
…
The line at the top of this page pins the label git:20260923.558b381, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_dp5hnffecwcupvur
GET https://markdownregistry.com/api/v1/resolve?ref=shinpr/ai-coding-project-boilerplate/requirement-convergence
GET https://markdownregistry.com/api/v1/blob/ace017345a3d45d9826195909c9e3945000448b5d2bc86ed6d002b969554a338
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
shinpr/ai-coding-project-boilerplate · .claude/skills-en/documentation-criteria/SKILL.md · Determines which PRD, ADR, UI Spec, Design Doc, and Work Plan a change requires and where each is stored. Use when…
shinpr/ai-coding-project-boilerplate · .claude/skills-en/frontend-typescript-rules/SKILL.md · Applies React/TypeScript type safety, component design, and state management rules. Use when implementing React…
shinpr/ai-coding-project-boilerplate · .claude/skills-en/frontend-typescript-testing/SKILL.md · Designs frontend tests using the repository's configured React test and browser harnesses, including RTL, MSW, Vitest…
shinpr/ai-coding-project-boilerplate · .claude/skills-en/implementation-approach/SKILL.md · Selects implementation strategy (vertical slice, horizontal, or hybrid) with risk assessment. Use when planning feature…
shinpr/ai-coding-project-boilerplate · .claude/skills-en/integration-e2e-testing/SKILL.md · Selects and designs the smallest integration/E2E test set that proves accepted behavior at an observable boundary. Use…
shinpr/ai-coding-project-boilerplate · .claude/skills-en/skill-optimization/SKILL.md · Evaluates and optimizes skill file quality using 9 content patterns and 10 editing principles. Use when creating…
shinpr/claude-code-workflows · skills/requirement-convergence/SKILL.md · Separates the outcome a change must produce from the requirements proposed to reach it, records what the user excluded…
shinpr/claude-code-workflows · dev-workflows-fullstack/skills/requirement-convergence/SKILL.md · Separates the outcome a change must produce from the requirements proposed to reach it, records what the user excluded…
shinpr/claude-code-workflows · dev-workflows/skills/requirement-convergence/SKILL.md · Separates the outcome a change must produce from the requirements proposed to reach it, records what the user excluded…
shinpr/claude-code-workflows · dev-skills/skills/requirement-convergence/SKILL.md · Separates the outcome a change must produce from the requirements proposed to reach it, records what the user excluded…
shinpr/claude-code-workflows · dev-workflows-frontend/skills/requirement-convergence/SKILL.md · Separates the outcome a change must produce from the requirements proposed to reach it, records what the user excluded…
shinpr/codex-workflows · .agents/skills/requirement-convergence/SKILL.md · Converges future-state requirements around outcome, exclusions, and rough cost. Use when users ask 'do we need this?'…
