agentleFS
Sign inStart free
foryouself83foryouself83/harness-tier/skills/design-sds/SKILL.md

design-sds

Skill10 starsChanged 31 days agoApache-2.0View on GitHub

Render the SDS in docs/sds/ to .docx after checking its FR links and coverage.

  • Installs packages

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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
  1. Very specific:

    When the second prints missing: ..., ask the user (structured choice) whether to install them, showing the command.

    line 33

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

Design-SDS

Converts the SDS as written — the files sds.template.md lists under sources, in that order — to <output>/sds.docx. Nothing here edits docs/sds/: it is reviewed text.

Precondition: .claude/harness-tier/scripts/design_doc_check.py must exist. If it doesn't, tell the user to run /flow-init and stop.

Interaction. Wherever this skill asks the user something, use the host's blocking question tool already in your tool list, matched by capability rather than by a host-specific name; if it is listed but not loaded, load it first with the host's tool-discovery primitive; only when no such tool is listed, or a question call errors, offer numbered options in chat and end your turn to wait for the reply — never answer the question yourself or skip it.

1. Resolve paths and dependencies

python3 .claude/harness-tier/scripts/design_doc_check.py --paths
python3 .claude/harness-tier/scripts/design_doc_render.py --check-deps

When the second prints missing: ..., ask the user (structured choice) whether to install them, showing the command. Yes → run python3 -m pip install python-docx markdown-it-py and continue. No → stop.

2. Check

python3 .claude/harness-tier/scripts/design_doc_check.py --templates
python3 .claude/harness-tier/scripts/design_doc_check.py --doc sds

A template violation → relay it and stop. A document violation → relay the list and ask the user (structured choice) whether to render anyway or stop so the SDS can be fixed first.

3. Render

python3 .claude/harness-tier/scripts/design_doc_render.py sds

The revision history comes from revisions in sds.template.md; tell the user to add a row there when this render is a new version.

4. Report

The .docx path, the violation count, and every warning: line.

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