agent-ixagent-ix/spec-skills/spec-write-us/SKILL.md

spec-write-us

Skill1 starsChanged 6 months agoMITView on GitHub

Write or format an ISO-compatible User Story (US) artifact.

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-us-to-frSkill
- spec-write-frSkill
- spec-write-itSkill
- spec-write-nfrSkill
- spec-write-strSkill

The file

We split this skill into the rules it gives an agent

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

≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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:
Use this skill to capture informative, non-normative user intent.
line 8
Distinctive:
No System Behavior: Describe intent, not implementation.
line 13
Distinctive:
Every US file MUST contain the following YAML frontmatter:
line 36

≈ “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.

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

Files

SKILL.md

Write User Story

Use this skill to capture informative, non-normative user intent.

Rules

Informative Only: Do not use normative language (SHALL).
No System Behavior: Describe intent, not implementation.
Format: As a [Role], I want [Goal], So that [Value].

Process

Identify: Role, Goal, Value.
Format: Use the standard template.
- Template: assets/user-story-template.md
- Example: assets/US-001-example.md
Extract Acceptance: Defined as Given/When/Then scenarios.
Context: Capture options and constraints as informative context.
Output: Save to correct location.
- Single Repo: spec/usecase/US-XXX-description.md
- Multi-Repo: specs/<category>/<component>/spec/usecase/US-XXX-description.md

Structure

Title: [US-XXX] Title
Story: Role/Goal/Value
Acceptance Criteria: US-XXX-AC-N

Frontmatter (Required)

Every US file MUST contain the following YAML frontmatter:

---
id: US-XXX
title: "<Title>"
artifact_type: US
relationships:          # Structured array of related FRs or StRs
  - target: "ix://org/repo/FR-XXX"
    type: "derives_into"
    cardinality: "1:N"
---

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