fred
Skill1 starsChanged 25 days agoApache-2.0View on GitHub
Bootstrap, migrate, and maintain the FRED methodology in a software repository. Use to set up FRED documents, coordinate parallel tracks, manage delivery gates, or review the project workflow. Routine slice specification and coding use create-fred and implement-fred when available.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- kansoku-trade/kansokutheir own version, first seen Sep 9, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- kansoku-trade/kansoku★ 322same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository2 other files it gives its agents.
- create-fredSkill
- implement-fredSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 10 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 21
When only fred is available, its template and references still support these tasks.
- Very specific: line 27
Read the project agent contract: prefer docs/agent-guides/00-AGENT-ENTRYPOINT.md, following applicable AGENTS.md instructions and README …
- Distinctive: line 37
If FRED docs are absent and the user wants this methodology, use references/bootstrap.md.
- Very specific: line 59
Keep files at docs/features/{NNN}-{kebab-slug}.md.
- Distinctive: line 69
Global check gate: before handing an implementation to review or signing off as Implemented or Closed, run the project's global check …
- Distinctive: line 81
After the global check, run additional QA (including browser or render inspection when relevant) only when the FRED's verification criteria …
- Distinctive: line 118
Create applicable OPERATIONS items while specifying the slice.
- Distinctive: line 123
Update existing architecture docs for changed durable contracts and boundaries, and project guides for changed procedures, before …
- Distinctive: line 141
When stopping with unfinished work or handing it off, leave concise resume notes in the FRED: baseline, completed/remaining work, checks, …
- Distinctive: line 146
Follow the project's Git/deploy rules and existing conversation authorization.
- Distinctive: line 150
Do not claim provider behavior from remembered SDK shapes or documentation browsing: check installed versions and relevant official docs, …
- Distinctive: line 163
Consider a separate skill only for a recurring, distinct workflow with clear inputs, outputs, and invocation boundaries.
- Distinctive: line 166
Keep FRED usable without companions, and preserve its global check gate.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
FRED
FRED = Feature Requirement Document. One implementation slice per file.
This skill supplies methodology and templates. Existing project documents and user instructions govern the consuming repository; templates are seeds.
For routine tasks, use available create-fred to gather requirements and write
or refine a slice, and implement-fred to select and execute agreed work.
Those skills read the consuming project's contract directly. Do not assume
optional siblings are installed or resolve them through relative source paths.
When only fred is available, its template and references still support these
tasks. Bootstrap and migration remain here; no model change or delegation is
implied by selecting a skill.
Start and route
- Read the project agent contract: prefer
docs/agent-guides/00-AGENT-ENTRYPOINT.md, following applicableAGENTS.mdinstructions and README pointers. Follow the project's documented workflow. - For planning, implementation, or “what next,” read
docs/features/ROADMAP.mdand the relevant FRED. For setup or delivery verification, also read the linked items indocs/features/OPERATIONS.md. - Load architecture and procedure guides relevant to the task through those pointers. Route by task, document responsibility, and section; read the source before relying on its contracts. Summaries aid discovery, not authority. Discover missing relevant documentation when necessary.
- If FRED docs are absent and the user wants this methodology, use references/bootstrap.md. Offer bootstrap when it has not been requested. Do not impose a competing spec system.
Existing projects may still use OPEN-FRED-INDEX.md and state folders. Follow
their contract until migration is requested; do not silently reorganize them.
Document responsibilities
| Document | Owns |
| Product / architecture | Intent, durable boundaries, contracts, decisions |
| Agent entrypoint / guides | Project workflow, commands, environment procedures |
| FRED | Slice scope, criteria, authoritative lifecycle state, evidence |
| ROADMAP | Stable IDs, tracks, priority, dependency and state summaries, claims, next actions |
| OPERATIONS | Setup tasks and shared delivery flows, their status and evidence |
Code establishes runtime facts. Resolve discrepancies with intended contracts; do not rewrite architecture or acceptance merely to justify incorrect code.
Lifecycle and sign-off
Keep files at docs/features/{NNN}-{kebab-slug}.md; update their status headers
and roadmap summaries without moving files. IDs are stable, not execution order.
| State | Meaning / gate |
| Draft | Scope or contracts need decisions. |
| Open | Approved slice with sufficiently defined scope, contracts, and implementation criteria; required implementation work or checks remain. |
| Implemented | Scoped behavior is in the project's designated integration baseline, required local checks pass, affected documentation is updated, and remaining delivery gates are linked. |
| Closed | Applicable review, setup, and delivery gates pass in the declared target environment, with evidence. |
Global check gate: before handing an implementation to review or signing off as Implemented or Closed, run the project's global check command from its documented working directory on the current work and require success. This command covers project-wide linting and formatting, including cascading checks across monorepo modules. Module-only checks do not replace it. Also run the slice's required behavioral checks. Record command, scope, result, date, and revision or working-tree context in the FRED. Rerun after subsequent changes before sign-off; a prior pass on different code is insufficient. A missing, blocked, or failing command blocks sign-off: report the cause and next action, retain the current state, and do not mark the checks passed. Planning-only Draft → Open does not require executing code checks.
After the global check, run additional QA (including browser or render inspection when relevant) only when the FRED's verification criteria or QA section calls for it. Prefer available browser tooling for UI/browser-shaped checks; report not-run honestly when tooling, auth, or environment is missing. Backend slices still need proportionate rule, authorization, persistence, and integration checks when those criteria apply. Defer shared deployed journeys and external setup, not slice correctness the FRED owns.
Deployable features close with preview or production evidence specifying which environment passed. Tooling and libraries close with relevant integration evidence. Implemented does not mean “most code exists”; mocks cannot establish an integrated outcome promised by the slice.
Tracks and dependencies
- Allocate the next unused ID from ROADMAP; never reuse an ID. Specify or deepen the slice before coding. Use templates/feature.md.
- Group ordered slices by bounded outcome and ownership. Identify shared prerequisites and contracts before opening independent tracks.
- Implementation prerequisites block coding or integration. An agreed contract and explicitly allowed fake may enable parallel work before the provider is implemented; record assumptions and the owner of real integration.
- Delivery gates block closure. Setup actually necessary to discover a contract or implement behavior must also be named as an implementation prerequisite. Downstream work need not wait for prerequisites to be Closed.
- For “next,” choose the highest-priority ready, unclaimed Open slice in the requested or roadmap-designated active track, or across tracks if neither is named. If that track has no eligible work, report its blocker rather than silently switching. Respect a named FRED's prerequisites. Readiness, claims, and blockers are roadmap fields, not states.
- Track scheduling does not authorize delegation, Git actions, or deployment.
Planning and state details: references/methodology.md. Implementation, review, and sign-off: references/agent-workflow.md.
Delivery and documentation
Create applicable OPERATIONS items while specifying the slice. Link their stable IDs from the FRED; keep execution steps and task status in OPERATIONS. One flow may validate several FREDs. Each Implemented FRED has a date and a next action or linked pending gate so deferred work remains visible.
Update existing architecture docs for changed durable contracts and boundaries, and project guides for changed procedures, before implementation sign-off. Reuse existing docs and scripts. Add conditional data, UX, migration, or policy detail only when relevant; there is no fixed eleven-section requirement.
Review and permissions
Independent review is optional unless the project or user requires it. Consider it for consequential changes and cross-track integration. Use an available reviewer/model within authorized scope; this skill does not require a provider or authorize paid model calls. Record required corrections separately from delivery gaps and optional improvements. Document and justify scope changes; never quietly weaken acceptance. Review approval does not replace execution.
Changes to acceptance, verification scripts, or CI/global-check scope need a recorded rationale under the project's decision process. Do not disable checks or narrow coverage just to obtain a pass; reviewers inspect these changes too.
When stopping with unfinished work or handing it off, leave concise resume notes in the FRED: baseline, completed/remaining work, checks, blocker, and next action. Refresh the current summary rather than adding a session transcript. On resume, compare notes with the actual checkout and relevant environment.
Follow the project's Git/deploy rules and existing conversation authorization; when committing, follow the entrypoint Git/PR policy (Conventional Commits by default). If silent, do not commit, push, open PRs, or deploy without a user request. Do not claim provider behavior from remembered SDK shapes or documentation browsing: check installed versions and relevant official docs, and record blocked live probes. Label fixtures. Keep secrets out of specs and evidence.
Bootstrap creates an entrypoint, FRED template, ROADMAP, and OPERATIONS, plus an optional root AGENTS pointer. Migration is explicit and preserves existing scope, IDs, history, and verification evidence; see bootstrap guidance.
Optional companion skills
The package includes create-fred and implement-fred for the recurring
specification and coding workflows. Shared project rules live in the entrypoint
and project documents; companions load the task guidance they need.
Consider a separate skill only for a recurring, distinct workflow with clear
inputs, outputs, and invocation boundaries. Project guides remain authority;
companions consume them and write results into existing FRED/OPERATIONS files.
Keep FRED usable without companions, and preserve its global check gate.
For candidate workflows, packaging versus project-local placement, and manual
invocation policies, read references/project-skills.md
when evaluating or adding further skills. Do not bootstrap a project skill suite
by default.
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.

