- name
SKILL.md
El archivo de la skill permanece en el repositorio del publicador.
Pega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add shinpr/ai-coding-project-boilerplate --skill requirement-convergence -a cursor -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add shinpr/ai-coding-project-boilerplate --skill requirement-convergence -a claude-code -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add shinpr/ai-coding-project-boilerplate --skill requirement-convergence -a codex -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add shinpr/ai-coding-project-boilerplate --skill requirement-convergence -a grok -yEnvía el mensaje copiado en un chat de Grok Bot. El Bot obtiene este SKILL.md de GitHub y lo añade a las skills que comparten todos tus Bots.
Install this skill: https://github.com/shinpr/ai-coding-project-boilerplate/tree/HEAD/.claude/skills-en/requirement-convergenceDel publicador
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, come after the what.
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 rather than 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 its own 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.
Use the available scope and cost evidence for both elicitation and judgment, then ask only for product choices that the repository cannot answer. Build requirements[] and the exclusion hearing from capabilities the user requested; an adjacent capability noticed during analysis stays out of both, so the user need not reject a capability they did not request. Repeat scope and cost analysis only when an answer changes the analysis target or required scope evidence.
Register these steps before starting and record each step's evidence as it completes:
When neither document exists, retain the record in the active context.
nonGoals as excluded from the current change and desired-future requirements as buildable scope. Evaluation requests, speculative ideas, prescribed mechanisms, and agent-proposed capabilities that were not promoted create no implementation obligation; an accepted ADR may retain evaluated options as decision history.weak-but-explicit field as a recorded open question rather than a settled decision, and escalate when the work depends on resolving it.nonGoals came from the user, or the user stated there are noneready, or weak-but-explicit by the user's agreementSeparates 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
---name: requirement-convergencedescription: Separates the outcome a change must produce from the requirements proposed to reach it, records what the user…---# .claude/skills-en/requirement-convergence/SKILL.mdResumen general
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.
Preguntas frecuentes
Descarga .claude/skills-en/requirement-convergence/SKILL.md desde el publicador, o copia la ruta y abre el repositorio. PlugMCP lista la skill y no aloja el archivo.
El publicador lo mantiene en https://github.com/shinpr/ai-coding-project-boilerplate.
Claude, Cursor, Codex y Grok Build pueden leer un SKILL.md que añadas desde el repositorio del publicador. Grok Bot lo instala cuando envías en un chat el enlace a la carpeta de la skill en GitHub.