Loading...
Loading...
Found 67 Skills
Structured specification with explicit scope boundaries: user stories, acceptance criteria, out-of-scope definition, risks, and estimation. Positions before feature-design in the feature lifecycle pipeline. Use when: "write spec", "user stories", "define requirements", "scope this", "what should this do", "acceptance criteria", "define scope"
Turn ambiguous or high-impact product and engineering changes into scoped, verifiable acceptance criteria before or alongside implementation. Use when a user asks to clarify a feature, define acceptance criteria, de-risk a security/data/migration/integration change, prepare implementation requirements for another agent, or make a complex request testable. Do not trigger for trivial edits, straightforward fixes, active debugging, code review, or implementation requests whose acceptance conditions are already clear unless the user explicitly invokes this skill.
Guardião da qualidade de stories e critérios de aceite no SynkOS. Use esta skill quando o usuário pedir para validar uma story antes da implementação, revisar critérios de aceite, aprovar ou rejeitar uma story para o sprint, verificar se o "definition of done" foi cumprido, ou fazer perguntas como "a story X está pronta para implementar?", "os critérios de aceite são testáveis?", "o escopo está claro?", "o que está IN e o que está OUT dessa story?". Ative também para refinar stories com escopo ambíguo, garantir rastreabilidade entre story e objetivo de produto, e para revisão pós-implementação contra os critérios originais.
Run verification checks for a task and evaluate results. Use when the user wants to verify a task's acceptance criteria.
Plans development tasks in a structured way for teams. Use this skill when the user triggers /plan-task with a description, or when asking to plan, detail, or break down a development task into steps. Always use when the message starts with /plan-task.
Turn a vague feature or product idea into an agreed, persisted specification through relentless structured questioning. Never assumes — every gap, ambiguity, or "probably" becomes a question to the developer, and the spec cannot be approved while open questions remain. Produces docs/specs/<NNN>-<slug>.md with acceptance criteria that /plan, /scaffold, and /tdd consume. Use when: "spec", "write a spec", "spec this out", "requirements", "PRD", "acceptance criteria", "define the feature", "user stories", "what should we build", or before planning any feature too big to describe in one sentence.
Development cycle validation gate (Gate 5) - validates all acceptance criteria are met and requires explicit user approval before completion.