Name: Sandcastle Cursor Flow
Author: leskraas

Use this skill to run the full .sandcastle workflow with Cursor prompts, not automation.

Phases

Operating rules

Keep one issue per implementation/review loop.
Reuse branch naming: sandcastle/issue-{number}-{slug}.
Prefer the prompt files in .sandcastle/ as canonical behavior.
For UI implementation, enforce shadcn-first composition and avoid custom inline components unless no shadcn option fits.
If a phase needs placeholders, ask for missing values once, then proceed.
After plan, apply deterministic issue selection:
- If there is exactly one unblocked issue, auto-select it and continue without asking.
- If there are multiple unblocked issues, provide a recommendation first, then ask the user to confirm.

Use this skill to run the full .sandcastle workflow with Cursor prompts, not automation.

Keep one issue per implementation/review loop.
Reuse branch naming: sandcastle/issue-{number}-{slug}.
Prefer the prompt files in .sandcastle/ as canonical behavior.
For UI implementation, enforce shadcn-first composition and avoid custom inline components unless no shadcn option fits.
If a phase needs placeholders, ask for missing values once, then proceed.
After plan, apply deterministic issue selection:
- If there is exactly one unblocked issue, auto-select it and continue without asking.
- If there are multiple unblocked issues, provide a recommendation first, then ask the user to confirm.