SDD Quick
Use this portable skill ($sdd-quick in Codex mentions) only for a precise bounded objective in
an initialized SDD Composy workspace. A quick task is a controlled entry path into the normal SDD
flow, not a shortcut around review, evidence, or verification.
Language: before writing human-facing prose, run scripts/sdd_language.py <repo-root> and use the persisted language; on not_initialized, return it with next_action: run_init. Localization rules: references/language.md.
Required protocol
- Inspect repository instructions and preserve unrelated changes.
- Reject or
ESCALATE before edits if more than five implementation files, architecture,
migration, destructive work, scope change, or unknown verification is involved. When a
machine-readable eligibility decision is needed, use the side-effect-free gate
scripts/sdd_quick.py <contract.json>.
- Read
templates/quick-contract.md and render the OKF QUICK_CONTRACT from it (keep its keys and headings), assign a Q-* identifier
(the Q-ID), and register a normal TASK-* record: render tasks/prd-<slug>/task-<id>.md from
templates/task.md and run scripts/sdd_tasks.py import; quick work never bypasses task
lifecycle gates and records its gate evidence with sdd_tasks.py evidence.
- Write and run a failing test before implementation (TDD). If it cannot be run, escalate.
- Implement only within the closed allowed-file list and run the known verification.
- Collect acceptance evidence, review, and verification. Append semantic events with
scripts/sdd_trace.py record <repo-root> --event <event.json> only after their actions
succeed; never write trace.json directly.
- Create the OKF
QUICK_REPORT from templates/quick-report.md, link all evidence from the
bundle index, verify the trace and artifact integrity, and publish a COMPLETE verified
verdict only when every gate passes. Otherwise report ESCALATED, REJECTED, or CAVEATS.
Never record prompts, output dumps, environment variables, secrets, models, or private paths. Do
not silently expand scope. If quick work needs a task synchronization, the plan-bound
CONFIRM-SDD-SYNC-… token of sdd-sync still applies.
Read when
references/quick.md — the eligibility gate is unclear, or when writing the contract (step 3)
and the report (step 7).
Safety: Do not commit, push, or publish. Do not read or expose .env, credentials, tokens, private keys, certificates, or fleet environment files. Full contract: references/safety.md.
1---2name: sdd-quick3description: >4 Deliver a small bounded change inside an initialized SDD Composy workspace through5 the quick path: at most five implementation files, a registered TASK, TDD,6 evidence, trace, and a verified verdict, escalating otherwise. Use for a precise7 objective with no existing task — 'ajuste rápido via SDD', 'quick fix under SDD',8 'small change to X in the SDD flow'. Do NOT use for an already registered task9 (sdd-execute), for architecture, migrations, or destructive work, or in10 repositories without SDD Composy (other plugins' quick).11metadata:12 source: https://skillmd.com/skills/pwdev-solucoes/sdd-quick13 version: 0.1.014---1516# SDD Quick1718Use this portable skill (`$sdd-quick` in Codex mentions) only for a precise bounded objective in19an initialized SDD Composy workspace. A quick task is a controlled entry path into the normal SDD20flow, not a shortcut around review, evidence, or verification.2122Language: before writing human-facing prose, run `scripts/sdd_language.py <repo-root>` and use the persisted language; on `not_initialized`, return it with `next_action: run_init`. Localization rules: `references/language.md`.2324## Required protocol25261. Inspect repository instructions and preserve unrelated changes.272. Reject or `ESCALATE` before edits if more than five implementation files, architecture,28 migration, destructive work, scope change, or unknown verification is involved. When a29 machine-readable eligibility decision is needed, use the side-effect-free gate30 `scripts/sdd_quick.py <contract.json>`.313. Read `templates/quick-contract.md` and render the OKF `QUICK_CONTRACT` from it (keep its keys and headings), assign a `Q-*` identifier32 (the Q-ID), and register a normal `TASK-*` record: render `tasks/prd-<slug>/task-<id>.md` from33 `templates/task.md` and run `scripts/sdd_tasks.py import`; quick work never bypasses task34 lifecycle gates and records its gate evidence with `sdd_tasks.py evidence`.354. Write and run a failing test before implementation (TDD). If it cannot be run, escalate.365. Implement only within the closed allowed-file list and run the known verification.376. Collect acceptance evidence, review, and verification. Append semantic events with38 `scripts/sdd_trace.py record <repo-root> --event <event.json>` only after their actions39 succeed; never write `trace.json` directly.407. Create the OKF `QUICK_REPORT` from `templates/quick-report.md`, link all evidence from the41 bundle index, verify the trace and artifact integrity, and publish a `COMPLETE` verified42 verdict only when every gate passes. Otherwise report `ESCALATED`, `REJECTED`, or `CAVEATS`.4344Never record prompts, output dumps, environment variables, secrets, models, or private paths. Do45not silently expand scope. If quick work needs a task synchronization, the plan-bound46`CONFIRM-SDD-SYNC-…` token of `sdd-sync` still applies.4748## Read when4950- `references/quick.md` — the eligibility gate is unclear, or when writing the contract (step 3)51 and the report (step 7).5253Safety: Do not commit, push, or publish. Do not read or expose `.env`, credentials, tokens, private keys, certificates, or fleet environment files. Full contract: `references/safety.md`.