SDD Execute
This portable skill implements exactly one ready task. The bundled scripts/sdd_execute.py
functions preflight, run_command, and finish are the deterministic execution boundary;
preserve their result fields and never create test-only bypasses.
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.
Contract
- Require exactly one
ready task and a successful dependency preflight.
- Require TDD RED evidence before implementation, enforce the task's allowed paths, and run the
declared verification commands, each as a real command. Record sanitized stdout/stderr, exit codes,
SHA-256 evidence, environment ownership, and cleanup.
- Never modify approved contracts or user-owned processes.
On success, record the passing verification run with scripts/sdd_tasks.py evidence <state> <TASK-ID> tests --status passed --ref <command-record> and request the guarded
running -> qa_required transition. A concrete dependency, environment, QA, evidence, or cleanup
blocker becomes blocked; a scope violation or rejected contract becomes rejected (both through
transition ... --reason <text>, from ready or running). Record the exact reason and next action, and stop on any QA or review
blocker.
Read when
references/execution.md — before the first run_command of a task (preflight fields, TDD
evidence, path and command rules, outcome classification).
references/states.md — a transition other than running -> qa_required is needed.
- The approved task contract (
tasks/prd-<slug>/task-<id>.md) — always, it is the input.
Output
Return the execution result, evidence manifest, changed paths, ownership and cleanup status, and
the permitted next lifecycle action.
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-execute3description: >4 Implement exactly one SDD Composy task in the ready state with dependency5 preflight, TDD RED evidence, allowed paths, real verification commands, and the6 guarded transition to qa_required. Use when a ready task should be executed —7 'executar a TASK-003', 'implementar a próxima tarefa', 'run task 4'. Do NOT use8 for changes without an approved task (sdd-quick), for autonomous multi-stage9 correction (sdd-loop), or for QA, review, or verification.10metadata:11 source: https://skillmd.com/skills/pwdev-solucoes/sdd-execute12 version: 0.1.013---1415# SDD Execute1617This portable skill implements exactly one `ready` task. The bundled `scripts/sdd_execute.py`18functions `preflight`, `run_command`, and `finish` are the deterministic execution boundary;19preserve their result fields and never create test-only bypasses.2021Language: 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`.2223## Contract2425- Require exactly one `ready` task and a successful dependency preflight.26- Require TDD RED evidence before implementation, enforce the task's allowed paths, and run the27 declared verification commands, each as a real command. Record sanitized stdout/stderr, exit codes,28 SHA-256 evidence, environment ownership, and cleanup.29- Never modify approved contracts or user-owned processes.3031On success, record the passing verification run with `scripts/sdd_tasks.py evidence <state>32<TASK-ID> tests --status passed --ref <command-record>` and request the guarded33`running -> qa_required` transition. A concrete dependency, environment, QA, evidence, or cleanup34blocker becomes `blocked`; a scope violation or rejected contract becomes `rejected` (both through35`transition ... --reason <text>`, from `ready` or `running`). Record the exact reason and next action, and stop on any QA or review36blocker.3738## Read when3940- `references/execution.md` — before the first `run_command` of a task (preflight fields, TDD41 evidence, path and command rules, outcome classification).42- `references/states.md` — a transition other than `running -> qa_required` is needed.43- The approved task contract (`tasks/prd-<slug>/task-<id>.md`) — always, it is the input.4445## Output4647Return the execution result, evidence manifest, changed paths, ownership and cleanup status, and48the permitted next lifecycle action.4950Safety: 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`.