How do I install the Doorstop Usage skill?

Run npx skillmds@latest add ksmyl/doorstop-usage in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Doorstop Usage safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Doorstop Usage?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Doorstop Usage free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Doorstop Usage?

ksmyl (@ksmyl) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Doorstop Usage by ksmyl — Agent Skill

Name: Doorstop Usage
Author: ksmyl

Doorstop Usage

How to use Doorstop for requirements traceability in Agent V. Use this skill whenever you need to run Doorstop commands (create, add, link, publish, review), understand the document tree structure, create or edit YAML requirement items, fix Doorstop validation warnings, or understand parent-child relationships between documents. Also use when you see Doorstop prefixes like STR, SYSRS, SWRS, SWARCH, SWDD, UT, SWIT, SYIT, SWQT, SYQT, or when dealing with traceability links, suspect links, or review hashes.

ksmyl 6ae4fdd 3 files · 6.0 KB Updated Sep 17, 2026

File contents

Doorstop Usage in Agent V

Document Tree

Agent V uses 11 Doorstop documents. Each stores YAML items under reqs/<PREFIX>/. Parent-child relationships enforce traceability — a child item must link to at least one parent item.

STR (Stakeholder Requirements)        <- root, no parent
└── SYSRS (System Requirements)       <- parent: STR
    ├── SYQT (System Qualification Tests)   <- parent: SYSRS
    ├── SYSARCH (System Architecture)       <- parent: SYSRS
    │   └── SYIT (System Integration Tests) <- parent: SYSARCH
    └── SWRS (Software Requirements)        <- parent: SYSRS
        ├── SWQT (SW Qualification Tests)   <- parent: SWRS
        └── SWARCH (SW Architecture)        <- parent: SWRS
            ├── SWIT (SW Integration Tests) <- parent: SWARCH
            └── SWDD (SW Detailed Design)   <- parent: SWARCH
                └── UT (Unit Tests)         <- parent: SWDD

Important: SYSARCH and SWARCH items are traceability anchors — lightweight index entries pointing to the real architecture documents in artifacts/. They enable automated link checking across the full V-model chain.

Essential Commands

# Validate entire tree (run this before writing GATE_PASSED)
uv run doorstop

# Add a new item to a document
uv run doorstop add SWRS          # Creates SWRS001, SWRS002, etc.

# Link a child item to a parent item
uv run doorstop link SWRS001 SYSRS001

# Cross-link (non-parent link, e.g., SWRS to SYSARCH per SWE.1.BP6)
uv run doorstop link SWRS001 SYSARCH001

# Mark all items as reviewed (clears suspect link warnings)
uv run doorstop review all

# Publish all documents to HTML/Markdown
uv run doorstop publish all reports/

Key Pitfalls (Summary)

ref field: Leave ref: '' unless pointing to a real file path on disk. Text strings cause validation errors.
Suspect links: Normal after parent modification. Fix with uv run doorstop review all.
Link direction: doorstop link CHILD PARENT — child links TO parent, not the reverse.
Empty documents: Warnings about empty docs are expected during pipeline execution.

Detailed References

For YAML item format and custom attributes by document type, read references/yaml-format.md.
For detailed pitfalls (ref field, suspect links, review hashes, empty documents, link direction), read references/pitfalls.md.

---name: doorstop-usagedescription: How to use Doorstop for requirements traceability in Agent V. Use this skill whenever you need to run Doorstop commands (create, add, link, publish, review), understand the document tree structure, create or edit YAML requirement items, fix Doorstop validation warnings, or understand parent-child relationships between documents. Also use when you see Doorstop prefixes like STR, SYSRS, SWRS, SWARCH, SWDD, UT, SWIT, SYIT, SWQT, SYQT, or when dealing with traceability links, suspect links, or review hashes.---# Doorstop Usage in Agent V## Document TreeAgent V uses 11 Doorstop documents. Each stores YAML items under `reqs/<PREFIX>/`. Parent-child relationships enforce traceability — a child item must link to at least one parent item.```STR (Stakeholder Requirements) <- root, no parent└── SYSRS (System Requirements) <- parent: STR ├── SYQT (System Qualification Tests) <- parent: SYSRS ├── SYSARCH (System Architecture) <- parent: SYSRS │ └── SYIT (System Integration Tests) <- parent: SYSARCH └── SWRS (Software Requirements) <- parent: SYSRS ├── SWQT (SW Qualification Tests) <- parent: SWRS └── SWARCH (SW Architecture) <- parent: SWRS ├── SWIT (SW Integration Tests) <- parent: SWARCH └── SWDD (SW Detailed Design) <- parent: SWARCH └── UT (Unit Tests) <- parent: SWDD```**Important:** SYSARCH and SWARCH items are traceability anchors — lightweight index entries pointing to the real architecture documents in `artifacts/`. They enable automated link checking across the full V-model chain.## Essential Commands```bash# Validate entire tree (run this before writing GATE_PASSED)uv run doorstop# Add a new item to a documentuv run doorstop add SWRS # Creates SWRS001, SWRS002, etc.# Link a child item to a parent itemuv run doorstop link SWRS001 SYSRS001# Cross-link (non-parent link, e.g., SWRS to SYSARCH per SWE.1.BP6)uv run doorstop link SWRS001 SYSARCH001# Mark all items as reviewed (clears suspect link warnings)uv run doorstop review all# Publish all documents to HTML/Markdownuv run doorstop publish all reports/```## Key Pitfalls (Summary)- **`ref` field:** Leave `ref: ''` unless pointing to a real file path on disk. Text strings cause validation errors.- **Suspect links:** Normal after parent modification. Fix with `uv run doorstop review all`.- **Link direction:** `doorstop link CHILD PARENT` — child links TO parent, not the reverse.- **Empty documents:** Warnings about empty docs are expected during pipeline execution.## Detailed References- For YAML item format and custom attributes by document type, read `references/yaml-format.md`.- For detailed pitfalls (ref field, suspect links, review hashes, empty documents, link direction), read `references/pitfalls.md`.

Frequently asked questions