sdd-draft-tasks
Installation
SKILL.md
Activation Contract
Use when drafting an OpenSpec tasks.md from an approved spec and design: an ordered, dependency-aware checklist. Works standalone or delegated by grill.
Hard Rules
- Follow the
grillingskill: one question at a time, recommendation attached, stop and wait; read spec/design context instead of asking when possible. - Follow the
native-question-uxskill for question presentation; ask one question at a time and stop after each answer. - Interview/summaries/gates use the user's language; artifacts default to English unless Spanish artifacts are explicitly requested.
- Plan-only: read-only codebase access; no code edits, builds, installs, tests, or state changes. Only write planning
.mdfiles after explicit approval. - Every task line MUST be
- [ ] X.Y {concrete action naming real files}: Specific, Actionable, Verifiable, Small enough for one session. Never vague ("implement feature"). Testing tasks reference specific spec scenarios. - Order groups by dependency: a task may only depend on earlier tasks; never forward-reference a later group. Execution scheduling (batching, parallelism, worktrees) is left to the implementer.
- Preserve the four Review Workload Forecast guard lines VERBATIM (the orchestraitor gates on them before implementing):
Decision needed before apply:,Chained PRs recommended:,Chain strategy:,400-line budget risk:. - Keep the artifact under 650 words. When delegated by grill, return the approved draft and do not write files; the orchestrator owns the single write step.