functional-analysis-group-writer
Skill1 starsChanged 55 days agoMITView on GitHub
Author phase-K group AFU (functional-analysis) markdown 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-writerSkill
- group-doc-finalizerSkill
- qa-reviewerSkill
- requirements-finalizerSkill
- requirements-group-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
3 rules. About 0 are common, 2 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 47
Every per-section draft under docs/_shared/_groups/<group_id>/_fa-group-sections/<lang>/*.md
- Distinctive: line 54
Do not invent functional analysis for them.
- Distinctive: line 68
Write only the languages and paths declared in the bundle.
≈ “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 — Day-1 contracts only. Mirrors per-file
functional-analysis-writerat group scope.
Scope
Owns phase-K authoring at the group level. One invocation per section
(per-section scope) or per group (finalizer scope), each covering exactly
bundle.languages in declared order at bundle.output_paths. Never add an
unrequested English edition or intermediate. Structural parity applies only
when multiple languages are requested.
Sibling skills:
functional-analysis-writer— per-file AFU (phase G).requirements-group-writer— group ATE (phase J).group-doc-finalizer— groupindex.md/complete.md(phase I).
Inputs
Per-section scope:
docs/_shared/_groups/<group_id>/_fa-group-bundles/<section_id>.bundle.json(authoritative)docs/_shared/_groups/<group_id>/_fa-group-bundles/<section_id>.bundle.md(LLM-facing)
Per-group finalizer scope:
docs/_shared/_groups/<group_id>/_fa-group-bundles/_finalize.bundle.{json,md}- Every per-section draft under
docs/_shared/_groups/<group_id>/_fa-group-sections/<lang>/*.md
Bundles aggregate, per group:
- Each eligible member's
docs/<lang>/<member>/functional-analysis.mdexcerpts (phase G). - PRC members and members with an upstream
_fa-bundles/_skipped.jsondecision are excluded from narrative inputs and recorded inbundle.skipped_members. Do not invent functional analysis for them. Other missing primary-language member documents are prerequisite errors (exit 4), not implicit skips. - Member narrative inputs and bundle excerpts use
<lang> = bundle.languages[0]; do not require an English intermediate or member inputs in every output language. - The group's
docs/<lang>/_groups/<group_id>/requirements.mdexcerpts (phase J) so AFU sections can cite group ATE requirement idsGRP-<group_id>-REQ-NNN. config/grouping.yamldescription + member list.- The active AFU profile (auto-detected per group).
Outputs
docs/_shared/_groups/<group_id>/_fa-group-sections/<lang>/<section_id>.mddocs/<lang>/_groups/<group_id>/functional-analysis.md
Write only the languages and paths declared in the bundle.
Determinism rules
- Citations point at group
requirements.md(forGRP-...-REQ-NNN) and per-filefunctional-analysis.mdof the owning member. - Member order follows
config/grouping.yaml.groups[*].members[*].
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.

