setup-workflow

Files (11)

• SKILL.md
• behavior-tests.md · references/
• catalog.md · references/
• check-commands-ci.md · references/
• code-checks.md · references/
• evaluations.md · references/
• project-guidance.md · references/
• project-skills.md · references/
• subagent-roles.md · references/
• test-data-isolation.md · references/
• user-journeys.md · references/

SKILL.md (first lines)

# setup-workflow

Read the [working agreement](../../references/workflow.md) unless it is already in this task's context. Use to establish or complete project setup. Read [project readiness](../../references/project-readiness.md). Plugin installation and version updates use [install-release](../install-release/SKILL.md).

Always assess the north star; jointly fill gaps and reuse suitable direction. Inspect user journeys, requirements, checks, prerequisites and guidance. For method assessment, proposals or selected work, read the [setup catalog](references/catalog.md) and relevant entries. Reuse coverage; explain gaps, changes, destinations and closing proof. Tests alone do not define correct behavior.

Follow the current phase: planning and inspection stay read-only without launching the product; implementation follows the applicable plan and assignment through the [implementation requirements](../../references/implementation-work.md). A setup request does not commission Auto-Work. Carry an accepted setup scope forward without asking again for each included component.

Establish the agreed north star and commissioned checks and guidance, then exercise affected routes and report actual coverage and limitations. Suitable existing setup needs no changes. For assessment or update of established setup, use [maintain-workflow](../maintain-workflow/SKILL.md).

From geldmacher/workflow, MIT.

More from geldmacher/workflow