Ss references

Skill lbk-open/super-spec/skills/ss-references

Agent Skills that take a requirement — or a production alert — to a reviewed pull request: multi-agent TDD coding, a parallel review panel with severity-graded verdicts, living OpenSpec-compatible specs, and per-language guardrails.

Install

npx -y skills add lbk-open/super-spec --skill ss-references

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

A library of shared templates that other ss-* skills read at runtime — subagent dispatch prompts, the technical-proposal template and its quality checklist, the OpenSpec directory skeleton, and the multi-repo detection rules. Not invoked directly by users; skills like ss-coding, ss-proposal, ss-write-spec, and the workflows read the file they need before producing an artifact.

SKILL.md

2.0 KB, as published. Nobody here has run it

Shared References

This skill is a template library, not a workflow. It has no standalone "run" behavior. Other skills read one of the files below at the exact point where they need to dispatch a subagent, generate an artifact, or make a routing decision.

What's Here

File	Covers	Read When
`implementer-prompt.md`	The dispatch prompt shape for implementer subagents	Before dispatching an implementer (`ss-coding`)
`proposal-template.md`	Section-by-section structure of a technical proposal	Before writing a proposal (`ss-proposal`)
`proposal-writing.md`	Quality-standards checklist a proposal must pass	During a proposal's self-review (`ss-proposal`)
`openspec-skeleton.md`	The `openspec/` directory skeleton for a project that has none	Before writing specs into a project without an `openspec/` tree (`ss-write-spec`, `ss-reverse-spec`)
`multi-repo-detection.md`	Rules for deciding whether a requirement spans repositories	At a workflow's entrance, and after a proposal records its repository list

How Other Skills Reach It

Skills reference these files by sibling relative path — ../ss-references/<file>.md — which resolves both in this repository and after an install flattens every skill directory into the same parent (~/.agents/skills/). This directory is a skill, and not a bare folder, precisely so that installers carry it along: the skills CLI only copies directories that contain a SKILL.md.