requirements-group-finalizer
Skill1 starsChanged 55 days agoMITView on GitHub
Phase-J per-group ATE finalizer for ONE group declared in `config/grouping.yaml`. LLM-driven. SCAFFOLD.
In this repository17 other files it gives its agents.
- chunk-text-extractionSkill
- cobol-chunkingSkill
- cobol-facts-extractionSkill
- diagram-rendererSkill
- facts-slicingSkill
- functional-analysis-finalizerSkill
- functional-analysis-group-finalizerSkill
- functional-analysis-group-writerSkill
- functional-analysis-writerSkill
- group-doc-finalizerSkill
- qa-reviewerSkill
- requirements-finalizerSkill
- requirements-group-writerSkill
- requirements-writerSkill
- section-doc-finalizerSkill
- section-doc-writerSkill
- technical-analysis-writerSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 36
Never require or create an unrequested English edition or intermediate.
- Distinctive: line 37
Check structural parity only when multiple languages are requested.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Status: scaffold. Mirror
.github/skills/requirements-finalizer/at group scope.
Scope
Phase-J finalizer step only. Authoring of per-section drafts is owned by
requirements-group-writer.
Inputs
docs/_shared/_groups/<group_id>/_req-group-bundles/_finalize.bundle.json(authoritative)docs/_shared/_groups/<group_id>/_req-group-bundles/_finalize.bundle.md(LLM-facing)docs/_shared/_groups/<group_id>/_req-group-sections/<lang>/*.md
Outputs
docs/<lang>/_groups/<group_id>/requirements.md
Finalize exactly bundle.languages in declared order at bundle.output_paths.
Never require or create an unrequested English edition or intermediate.
Check structural parity only when multiple languages are requested.
Determinism rules
- Section order in the finalized file follows the bundle's
section_order[]. - Requirement ids are taken verbatim from per-section drafts; no renumbering across sections.
- Cross-cutting "Group summary" header includes member list verbatim
from
config/grouping.yaml.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

