project-sprints

Files (1)

• SKILL.md

SKILL.md (first lines)

!`bash ${CLAUDE_SKILL_DIR}/../../hooks/read-state.sh session-state`

```bash
source "${CLAUDE_PLUGIN_ROOT}/hooks/sc-artifact.sh"

# Load active sprint if one exists
ACTIVE_SPRINT=$(python3 "${_sc_hooks}/sc-artifact-impl.py" \
  query "$SC_PROJECT_ROOT" "$SC_PRODUCT_BASE" "$SC_STATE_BASE" \
  sprint status=active 2>/dev/null | python3 -c "
import json,sys
items=json.load(sys.stdin)
print(items[0]['id'] if items else 'NONE')
" 2>/dev/null || echo "NONE")

echo "ACTIVE_SPRINT=$ACTIVE_SPRINT"
```

# Project Sprints

Manage sprints: plan, activate, track, and close. Arguments: `$ARGUMENTS`

---

## MODE CHECK

Read `mode` from pre-loaded session state (or `cat .sweetclaude/state/effective-gates.yaml 2>/dev/null | grep "^mode:"`)

If `mode` is `flow`, `kanban`, or `shape_up`, output and stop:

> "This skill is not active in **{mode}** mode.
>
> - **Flow and Kanban** use continuous delivery without sprint cadence. Track work with `/sweetclaude:build project-issues`.
> - **Shape Up** uses fixed-time cycles with pitches, not sprints. Create issues from a pitch with `/sweetclaude:build project-issues`.
>
> To use sprint tracking, shift to Agile mode: `/sweetclaude:configure project-mode shift agile`"

Proceed only if `mode` is `agile` (or unset).

---

## Routing

| Arguments | Operation |
|---|---|
| (empty) | → **Status** — active sprint board or summary |
| `list` | → **List** all sprints |
| `new` | → **Plan** a new sprint |
| `start <SP-NNN>` | → **Activate** a planned sprint |
| `board` | → **Board** view of active sprint |
| `update <ID>` | → **Update** an issue on the active sprint |
| `close` | → **Close** the active sprint |
| `retro` | → **Retrospective** for the most recently closed sprint |

---

## Status (default)

If `ACTIVE_SPRINT` is `NONE`:

```bash
source "${CLAUDE_PLUGIN_ROOT}/hooks/sc-artifact.sh"
sc_artifact_query sprint status=planned
```

If planned sprints exist: "No active sprint. Next planned: {SP-NNN} — {title}. Run `project-sprints start {SP-NNN}` to begin."
If no planned sprints either: "No sprints. Run `project-sprints new` to plan one."

If `ACTIVE_SPRINT` is set, run the **Board** operation (below).

---

## List

```bash
source "${CLAUDE_PLUGIN_ROOT}/hooks/sc-artifact.sh"
sc_artifact_list sprint
```

Present as table, newest first:

```
ID      Title         Status    Milestone  Start       End         Velocity
─────────────────────────────────────────────────────────────────────────────
SP-003  Sprint 3      active    MS-001     2026-05-06  2026-05-20  —
SP-002  Sprint 2      complete  MS-001     2026-04-22  2026-05-06  8
SP-001  Sprint 1      complete  (none)     2026-04-08  2026-04-22  5
```

---

## New (Plan a sprint)

Check for existing active sprint first:

```bash
source "${CLAUDE_PLUGIN_ROOT}/hooks/sc-artifact.sh"
sc_artifact_query sprint status=active
```

If one exists: "Sprint {ID} is already active. Close it before planning a new one, or plan ahead — the new sprint won't start until you explicitly activate it."

Ask, one question at a time:

1. **Title** — "What's this sprint called? (e.g. 'Sprint 4' or 'Sprint 2026-05-20')"
2. **Milestone** — Load milestones first:

```bash
source "${CLAUDE_PLUGIN_ROOT}/hooks/sc-artifact.sh"
sc_artifact_list milestone
```

"Which milestone is this sprint building toward? (e.g. MS-001, or press enter to skip)"

3. **Start date** — "Start date? (YYYY-MM-DD)"
4. **End date** — "End date? (YYYY-MM-DD)"
5. **Goal** — "What's the sprint goal — the one sentence that describes what's true when this sprint succeeds?"
6. **Capacity notes** — "Any known interruptions or reduced availability? (or press enter to skip)"

From carson-sweet/sweetclaude, AGPL-3.0.

More from carson-sweet/sweetclaude