agentleFS
Sign inStart free
NashEQifyNashEQify/forge/.claude/skills/source-spec-reduce/SKILL.md

source-spec-reduce

Skill2 starsChanged 3 days agoMITView on GitHub

Post-authoring source-spec reduction — cut each absorbed section, leave a pointer stub, archive the source when fully dissolved. Triggers when a source spec's sections have been absorbed and need pointer-stub reduction (build specify); NOT for a greenfield spec with no source predecessor.

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read and follow framework/work-principle.md before taking up work.

    line 10
  2. Very specific:

    Read the SoT and follow it.

    line 19

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Skill: source-spec-reduce (Wrapper)

<!-- generated-by: scripts/generate_skill_wrappers.py (do not hand-edit) -->

Read and follow framework/work-principle.md before taking up work. Resolve it against the same framework root as the SoT; retain the consumer CWD.

This is the Claude-Code-discoverable wrapper. The full orchestrator-neutral protocol — methodology, contract, modes, red flags — lives in the SoT:

SoT: skills/source_spec_reduce/SKILL.md

Read the SoT and follow it. This wrapper is a generated derived artifact (scripts/generate_skill_wrappers.py); it exists only so Claude Code can inject the skill into the available-skills system-reminder for proactive discovery. Do not hand-edit — edits are reverted on the next generator run and flagged by consistency_check.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free