Geo Proposal
sickn33/agentic-awesome-skills
Auto-generate a professional, client-ready GEO service proposal from audit data.
Separates the outcome a change must produce from the requirements proposed to reach it, records what the user excluded, and bands cost from structure.
MITAuto-check passed
Install Requirement Convergence
$ npx skills add shinpr/claude-code-workflows --skill requirement-convergence -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install shinpr/claude-code-workflows requirement-convergence --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/shinpr/claude-code-workflows.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/requirement-convergence .claude/skills/requirement-convergence && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "requirement-convergence" agent skill from https://github.com/shinpr/claude-code-workflows/tree/main/skills/requirement-convergence into .claude/skills/requirement-convergence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "requirement-convergence", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/shinpr/claude-code-workflows/tree/main/skills/requirement-convergenceType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add shinpr/claude-code-workflows --skill requirement-convergence -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install shinpr/claude-code-workflows requirement-convergence --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/shinpr/claude-code-workflows.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/requirement-convergence .agents/skills/requirement-convergence && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "requirement-convergence" agent skill from https://github.com/shinpr/claude-code-workflows/tree/main/skills/requirement-convergence into .agents/skills/requirement-convergence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "requirement-convergence", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add shinpr/claude-code-workflows --skill requirement-convergence -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install shinpr/claude-code-workflows requirement-convergence --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/shinpr/claude-code-workflows.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/requirement-convergence .cursor/skills/requirement-convergence && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "requirement-convergence" agent skill from https://github.com/shinpr/claude-code-workflows/tree/main/skills/requirement-convergence into .cursor/skills/requirement-convergence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "requirement-convergence", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/shinpr/claude-code-workflows.git --path skills/requirement-convergence--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add shinpr/claude-code-workflows --skill requirement-convergence -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install shinpr/claude-code-workflows requirement-convergence --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/shinpr/claude-code-workflows.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/requirement-convergence .gemini/skills/requirement-convergence && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "requirement-convergence" agent skill from https://github.com/shinpr/claude-code-workflows/tree/main/skills/requirement-convergence into .gemini/skills/requirement-convergence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "requirement-convergence", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install shinpr/claude-code-workflows requirement-convergenceInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add shinpr/claude-code-workflows --skill requirement-convergence -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/shinpr/claude-code-workflows.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/requirement-convergence .github/skills/requirement-convergence && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "requirement-convergence" agent skill from https://github.com/shinpr/claude-code-workflows/tree/main/skills/requirement-convergence into .github/skills/requirement-convergence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "requirement-convergence", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add shinpr/claude-code-workflows --skill requirement-convergence -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install shinpr/claude-code-workflows requirement-convergence --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/shinpr/claude-code-workflows.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/requirement-convergence .opencode/skills/requirement-convergence && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "requirement-convergence" agent skill from https://github.com/shinpr/claude-code-workflows/tree/main/skills/requirement-convergence into .opencode/skills/requirement-convergence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "requirement-convergence", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
requirement-convergence- GitHub stars
- 694
- Token cost
- ~1.5k tokens
- SKILL.md length
- 820 words
- Files
- 2 (incl. references)
- Skills in repo
- 30
- Repo updated
- First seen
- Licence
- MIT
At a glance
Separates the outcome a change must produce from the requirements proposed to reach it, records what the user excluded, and bands cost from structure.
- Works in 3 steps: Read the convergence record from the… → Treat nonGoals as excluded from the… → Treat a weak-but-explicit field as a…
- A requirement enters a workflow
- SKILL.md covers Purpose, Convergence Fields, Hearing Protocol and Scope Confirmation, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Requirement Convergence is an agent skill from shinpr/claude-code-workflows. 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.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/criteria.md`).
The repository describes itself as: Development workflows for Claude Code that keep broad exploration focused on the outcome you approved. The licence is MIT.
When your agent uses it
- A requirement enters a workflow
- Before design begins
Example prompts
- “Use the requirement-convergence skill to separate the outcome a change must produce from the requirements proposed to reach it, records what the…”
- “/requirement-convergence”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Read the convergence record from the prompt.
- Treat nonGoals as excluded from the current change and desired-future requirements as buildable scope. Evaluation requests, speculative…
- Treat a weak-but-explicit field as a recorded open question rather than a settled decision. When work depends on it, return the missing…
What it can do on your machine
Read from SKILL.md and the folder at commit a4ecd62. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Requirement Convergence loads about 1.5k tokens when it runs, and up to ~2.5k if it reads all its reference files. Until then it costs about 60 tokens; SKILL.md has 820 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from shinpr/claude-code-workflows at commit a4ecd62, republished under its MIT licence (© shinpr). 820 words, ~1,525 tokens.
Download SKILL.mdSave it as
.claude/skills/requirement-convergence/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- requirement-convergence
- description
- 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.
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.
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.
Register these steps before starting and record each step's evidence as it completes:
| Step | Action | Completion evidence |
|---|---|---|
| 1 | Render the Scope Confirmation below, asking only about the fields below ready | Each fact cites the analysis output it came from, and User decisions holds one question per field below ready |
| 2 | Record each answer as that field's value | The value uses wording the user supplied, not wording the hearing offered |
| 3 | Re-ask once when a recorded value still fails its pass condition, then mark the field weak-but-explicit when the user agrees to leave the second answer as it stands | Two recorded answers, or the user's agreement to stop |
| 4 | Hand the record to the step that judges the fields | An updated record returned from that step |
Step 2's evidence is what keeps the hearing reviewable: a value restating the hearing's own candidates fails it, so the user's judgment survives however the question was put.
Show full SKILL.md (398 more words)Show less
Scope Confirmation
Render this shape at every requirements confirmation stop, whether or not the hearing ran, using only what can change the user's requirement decision or the workflow route.
| Section | Contents |
|---|---|
| Confirmed scope | The requirements and exclusions the user has already selected, in the user's wording |
| Decision evidence | Each material observed fact with its source, followed by what that fact can change about scope, outcome, or cost |
| User decisions | Each unresolved product, UX, or operational question, followed by the scope, outcome, or cost effects of its materially different answers |
| Workflow | Rough cost band with the unknowns that remain, Structural Scale, and the selected document and workflow route |
Keeping the first three sections separate is what makes the decision informable: merged, the reader cannot tell which line is the user's own settled boundary, which is a repository observation, and which is still open.
Only an explicit user answer moves an item from User decisions into Confirmed scope. Because Step 2 records the user's own wording, pose each open decision as a question and let the user supply its answer. The orchestrator owns Workflow and presents it as a selected route.
Storage Protocol
| Carrier | Holds | Written by |
|---|---|---|
| The convergence record in the judging step's output | Every field with its readiness label | The judging step |
PRD Success Criteria and Future / Out of Scope | outcome; user-authored nonGoals | The PRD production step |
Design Doc Requirement Convergence | The same when no PRD exists, and the fields left weak-but-explicit in every case | The Design Doc production step |
A flow that produces neither document carries the record in its own context to the next step.
Reference Protocol (For Downstream Consumers)
- Read the convergence record from the prompt.
- Treat
nonGoalsas excluded from the current change anddesired-futurerequirements as buildable scope. Evaluation requests, speculative ideas, prescribed mechanisms, and agent-proposed capabilities that were not promoted create no downstream obligation; an accepted ADR may retain evaluated options as decision history. - Treat a
weak-but-explicitfield as a recorded open question rather than a settled decision. When work depends on it, return the missing decision and its effect to the owning workflow.
Quality Checklist
- Scope facts were presented before questions were asked
-
nonGoalscame from the user, or the user stated there are none - Every applicable field is
ready, orweak-but-explicitby the user's agreement
References
- references/criteria.md — judgment rules per field, cost inputs, challenge intensity, solution-in-disguise test
© shinpr, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in skills/requirement-convergence of shinpr/claude-code-workflows.
- SKILL.md
- references/criteria.md
Open the folder on GitHubat commit a4ecd62
Compare with similar skills
Requirement Convergence next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Requirement Convergence this skillshinpr/claude-code-workflows | 694 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Geo Proposalsickn33/agentic-awesome-skills | 47k | 1 repos | ~3.2k | Automated safety check: Notes | MIT | |
| Requirement Convergenceshinpr/ai-coding-project-boilerplate | 234 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Better Proposals AutomationComposioHQ/awesome-claude-skills | 77k | 3 repos | ~764 | Automated safety check: Pass | None | |
| Requirementsrizsotto/Bear | 6.5k | — | ~2k | Automated safety check: Pass | GPL-3.0 | |
| Contract And Proposal Writeralirezarezvani/claude-skills | 28k | 2 repos | ~3.4k | Automated safety check: Pass | MIT |
Similar skills
Requirement Convergence
shinpr/ai-coding-project-boilerplate
Separates the outcome a change must produce from the requirements proposed to reach it, records what the user excluded, and bands cost from structure.
Better Proposals Automation
ComposioHQ/awesome-claude-skills
Automate Better Proposals tasks via Rube MCP (Composio). An agent skill from ComposioHQ/awesome-claude-skills.
Requirements
rizsotto/Bear
Write, modify, or review a requirement file under docs/requirements -- pick the single owning file, keep the text contract-only, name IDs so they need no explanation, and verify cross-references and…
Contract And Proposal Writer
alirezarezvani/claude-skills
Generate professional, jurisdiction-aware business documents: freelance contracts, project proposals, SOWs, NDAs, and MSAs.
Proposal
Chorus-AIDLC/Chorus
Chorus Proposal workflow on Hermes — create proposals with document and task drafts, manage dependency DAG, validate, submit, and run the read-only proposal reviewer via delegatetask.
More from shinpr/claude-code-workflows
All 30 skills in this repoIntegration E2E Testing
shinpr/claude-code-workflows
Integration and E2E test design principles, ROI calculation, test skeleton specification, and review criteria.
AI Development Guide
shinpr/claude-code-workflows
Applies language-agnostic and backend technical decision criteria, anti-pattern detection, debugging, and quality gates.
Frontend AI Guide
shinpr/claude-code-workflows
Applies React/TypeScript-specific technical decision criteria, anti-pattern detection, debugging, and frontend quality gates.
Implementation Approach
shinpr/claude-code-workflows
Implementation strategy selection framework. An agent skill from shinpr/claude-code-workflows.
Recipe Quality Profile
shinpr/claude-code-workflows
Proposes repository-specific quality policy for implementation and review and, after confirmation, creates or updates docs/project-context/quality.yaml.
Subagents Orchestration Guide
shinpr/claude-code-workflows
Guides subagent coordination through implementation workflows.
Questions about Requirement Convergence
What does Requirement Convergence do?
Separates the outcome a change must produce from the requirements proposed to reach it, records what the user excluded, and bands cost from structure. Requirement Convergence is an agent skill from shinpr/claude-code-workflows. Separates the outcome a change must produce from the requirements proposed to reach it, records what the user excluded, and bands cost from structure.
When should I use Requirement Convergence?
Requirement Convergence fits situations like: A requirement enters a workflow; before design begins.
How do I install Requirement Convergence in Claude Code?
Run `npx skills add shinpr/claude-code-workflows --skill requirement-convergence -a claude-code`. Or copy the skill folder (skills/requirement-convergence in shinpr/claude-code-workflows) into .claude/skills/requirement-convergence in your project. Claude Code loads it when a task matches its description.
How do I install Requirement Convergence in Codex?
Run `npx skills add shinpr/claude-code-workflows --skill requirement-convergence -a codex`. Or copy the skill folder (skills/requirement-convergence in shinpr/claude-code-workflows) into .agents/skills/requirement-convergence in your project. Codex loads it when a task matches its description.
Can I use Requirement Convergence in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add shinpr/claude-code-workflows --skill requirement-convergence -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/requirement-convergence, .gemini/skills/requirement-convergence, .github/skills/requirement-convergence and .opencode/skills/requirement-convergence in your project.
What does Requirement Convergence need to run?
SKILL.md names no scripts, command-line tools or credentials: Requirement Convergence is instructions for the agent only.
Does Requirement Convergence access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Requirement Convergence safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Requirement Convergence use?
Requirement Convergence is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Requirement Convergence use?
About 1.5k tokens (SKILL.md is roughly 6.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 943 tokens, read only when the agent opens those files.
What are the alternatives to Requirement Convergence?
Skills that share tags, products or a category with Requirement Convergence: Geo Proposal (sickn33/agentic-awesome-skills, 47k stars), Requirement Convergence (shinpr/ai-coding-project-boilerplate, 234 stars), Better Proposals Automation (ComposioHQ/awesome-claude-skills, 77k stars) and Requirements (rizsotto/Bear, 6.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Requirement Convergence?
shinpr (a GitHub user) maintains it in shinpr/claude-code-workflows, which has 694 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on October 1, 2026.
Source: shinpr/claude-code-workflows on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.