design-doc-generator
Activate when the user wants to produce a technical design document from existing requirements, specifications, or a PRD. Use this skill to convert the outputs of prd-creator, requirements-tracer, specification-driven-development, and architecture-decision-records into a single, implementation-ready DESIGN.md that engineers can build from. Also trigger for: "write the design doc", "technical design", "system design", "how should we build this", "design document", "architecture doc", "translate specs to design", "what does the implementation look like", "design from requirements", "component design", "data flow design", "turn the PRD into a design".
Repository SourceNeeds Review
requirements-tracer
Converts business goals into testable, traceable requirements and keeps them linked to everything built from them. Use this skill whenever the user wants to: decompose a high-level business ask into user stories with BDD acceptance criteria, write Given/When/Then test scenarios, maintain or query the traceability matrix linking requirements to code and tests, detect orphaned code with no requirement, detect requirements with no implementation, or analyse the impact of a scope change. Also trigger for: "what does done mean", "what are we actually building", "scope creep", "is this in scope", "traceability", "BDD", "given when then", "user story", "feature breakdown", "requirements quality".
Repository SourceNeeds Review
stakeholder-sync
Activate when keeping external stakeholders (clients, users, partners, leadership) aligned. Use when: setting communication cadence, drafting a status update, logging a decision that affects someone outside the team, handling a scope change request, writing a difficult message, or calibrating tone for a non-technical audience. Also trigger on: "how do I tell the client", "weekly update", "they're asking for scope changes", "we need to escalate", "I need to document what was agreed".
Repository SourceNeeds Review
executable-acceptance-verification
Activate when writing or reviewing executable acceptance tests, converting requirements into BDD scenarios, running acceptance test suites to determine whether a feature meets the agreed acceptance criteria, writing the acceptance test plan for a milestone, verifying that all acceptance criteria from the requirements tracer are covered by tests, or producing an objective sign-off report for a milestone. Use when "done" needs to be verifiable by code, not a matter of opinion.
Repository SourceNeeds Review