Workbench GSD Tasking

Use this skill to turn approved requirements, product designs, or technical designs into executable tasks.

Tasking Standard

• Each task has one owner, one outcome, one evidence requirement, and one verification path.
• Parallelize only when write scopes or live mutation surfaces are clearly separate.
• Put approval gates before live mutations, destructive changes, external posts, billing changes, or broad binding updates.
• Include rollback or recovery evidence for live resource updates.
• Keep smoke tests separate when they depend on committed source or synchronized live state.

Task Shape

For each task, include:

• ID
• OWNER
• OBJECTIVE