Spec-Linked Documentation (SLD): Language-agnostic discipline for maintaining bidirectional traceability between functional specifications and source-code docstrings via stable identifiers and CI validation. Optional/opt-in adoption. Builds on OpenFastTrace and DO-178C Requirements Traceability Matrix traditions.
Requirements grilling for engineering tasks. Use before writing any code when the task's goal, boundaries, acceptance criteria, failure modes, priorities, or non-goals are not yet settled — interrogate the user across six dimensions, reach consensus, record a structured spec, and only then implement.
Use this skill to generate well-branded interfaces and assets for Reqvire (the Reqvire Explorer — a Git-native MBSE knowledge-graph viewer), either for production or throwaway prototypes/mocks/etc. Contains essential design guidelines, colors, type, fonts, assets, and UI kit components for prototyping.
Assemble a context package (code graph, requirements, constraints, blast radius) before a downstream generation task runs - human-approved, source-attributed. Do NOT use for simple lookups.
Take a rough idea from the user (a few lines of text), summarize it, then act as a domain-expert product manager to interactively refine it into a full requirement document and MVP plan. Use when someone says "I have an idea", "help me build X", "turn this into a product", "what would the MVP look like", or provides a…
Build, review, update, and audit production-grade project documentation packs from a brief, partial docs, or implementation changes. Use when the user asks to create a full docs folder, PRD/FRS/NFR, architecture docs, ERD/data dictionary, API/OpenAPI docs, UX flows, project plans, engineering workflow docs, AI agent…
★not rated 1 3mo agoA94 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: