spec-us-to-fr
Skill1 starsChanged 6 months agoMITView on GitHub
Derive normative Functional Requirements (FR) from User Stories (US).
In this repository19 other files it gives its agents.
- spec-app-reviewSkill
- spec-blueprintSkill
- spec-dependency-analysisSkill
- spec-evidence-analysisSkill
- spec-failure-domain-analysisSkill
- specifySkill
- spec-integrity-analysisSkill
- spec-matrixSkill
- spec-object-reviewSkill
- spec-reviewSkill
- spec-risk-complexity-analysisSkill
- spec-scope-boundary-analysisSkill
- spec-security-analysisSkill
- spec-to-planSkill
- spec-write-frSkill
- spec-write-itSkill
- spec-write-nfrSkill
- spec-write-strSkill
- spec-write-usSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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
- Distinctive: line 14
No copying: Translate to technical specification, do not copy story text.
- Very specific: line 31
Use spec-write-fr with the appropriate domain template.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Convert User Story to Functional Requirement
Transform informative user intent into normative system behavior.
Rules
- Atomic: Decompose story into specific atomic behaviors.
- Normative: Use
SHALL/SHALL NOT. - No copying: Translate to technical specification, do not copy story text.
- Verifiable: Must have independent acceptance criteria.
Process
- Analyze: Identify system responsibilities in the
US-XXX. - Decompose into typed FRs:
- Behavioral: API logic, business rules (standard template).
- Entity: Data models with typed fields (
domain: entity). - Event: Domain events emitted (
domain: event). - API Endpoint: REST endpoints (
domain: api_endpoint). - Queue: Message contracts (
domain: queue). - Process: End-to-end workflows (
domain: process). - State Machine: Entity lifecycles (
domain: state_machine). - Config: Configuration schemas (
domain: configuration). - Full list:
spec-write-frobject-type-guide.md.
- Create FRs:
- Use
spec-write-frwith the appropriate domain template. - Link back to
US-XXX.
- Use
- Define:
- Inputs/Outputs: Typed and validated.
- Error Handling: Failure modes.
- Constraints: Technical limits (not options).
- Save to correct location:
- Single Repo:
spec/functional/FR-XXX-description.md - Multi-Repo:
specs/<category>/<component>/spec/functional/FR-XXX-description.md
- Single Repo:
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.