agentleFS
Sign inStart free
agent-ixagent-ix/spec-skills/spec-write-str/SKILL.md

spec-write-str

Skill1 starsChanged 6 months agoMITView on GitHub

Write an authoritative Stakeholder Requirement (StR).

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill to capture normative, outcome-focused stakeholder needs.

    line 8
  2. Distinctive:

    Every StR file MUST contain the following YAML frontmatter:

    line 38

≈ “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 Stakeholder Requirement

Use this skill to capture normative, outcome-focused stakeholder needs.

Rules

  • Outcome Focused: What must be satisfied, not how.
  • Implementation Agnostic: No system internals or APIs.
  • Normative: May use SHALL to express stakeholder obligation.

Process

  1. Identify Need: Source from users, policies, or contracts.
  2. Use Template:
    • Source: assets/stakeholder-requirement-template.md
  3. Define Sections:
    • Statement: Concise, clear expectation.
    • Rationale: Why it matters (value, risk).
    • Context: Operating environment/constraints.
    • Success Indicators: Illustrative outcomes (not test steps).
  4. Output: Save to correct location.
    • Single Repo: spec/stakeholder/StR-XXX-description.md
    • Multi-Repo: specs/<category>/<component>/spec/stakeholder/StR-XXX-description.md

Validation

  • Is it authoritative?
  • Is it implementation-free?
  • Are dependencies documented strictly in the YAML frontmatter relationships array?

Frontmatter (Required)

Every StR file MUST contain the following YAML frontmatter:

---
id: StR-XXX
title: "<Title>"
artifact_type: StR
relationships:          # Structured array of impacted features
  - target: "ix://org/repo/FR-XXX"
    type: "satisfied_by"
    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