all

Included with Lifetime

$97 forever

Execute all remaining sprints sequentially

General

What this skill does


# Sprint All — Continuous Sprint Execution

Execute all remaining sprints from the sprint plan sequentially. Each sprint invokes `/sprint:cycle`, with inter-sprint gates to verify completion.

## Dynamic Context

```
!cat sprint.config.yaml 2>/dev/null || echo "NO_CONFIG"
!cat $(grep 'memory_file:' sprint.config.yaml 2>/dev/null | awk '{print $2}') 2>/dev/null | head -40
!cat $(grep 'sprint_plan:' sprint.config.yaml 2>/dev/null | awk '{print $2}') 2>/dev/null | head -30
!gh issue list --state open --limit 30 2>/dev/null
```

## Arguments

`$ARGUMENTS` — Starting sprint number (optional). Auto-determined if omitted.

e.g. `5` → Execute Sprint 5 through the end

---

## Prerequisites

1. **`sprint.config.yaml` required**: If missing, guide to `/sprint:init`
2. **Sprint plan document required**: If missing, guide to `/sprint:plan`
3. All previous sprints must be complete before starting

---

## Procedure

### 1. Status Assessment

1. Load `sprint.config.yaml`
2. Parse sprint plan document → extract full sprint list
3. Identify completed sprints from MEMORY.md + GitHub issue status
4. Determine remaining sprints

### 2. Execution Plan Output

```
Sprint Overview:

| Sprint | Goal | Status |
|--------|------|--------|
| Sprint 1 | Foundation | Completed |
| Sprint 2 | Crawlers | Completed |
| Sprint 3 | API + Dashboard | Pending |
| Sprint 4 | Notifications | Pending |
| ...    | ... | ... |

Execution target: Sprint 3 ~ Sprint {N}
```

### 3. User Confirmation

**Gate**: "Execute Sprint {start} ~ Sprint {end} sequentially. Proceed?"

### 4. Continuous Execution Loop

```
for each sprint in remaining_sprints:
    1. Notify user: "Starting Sprint {N}"
    2. Invoke /sprint:cycle {N} (Phase 0-7 full)
    3. Verify sprint completion:
       - All issues closed
       - All PRs merged
       - MEMORY.md updated
    4. Gate: "Sprint {N} complete. Proceed to Sprint {N+1}?"
       - Approved → next sprint
       - Rejected → stop + report current status
```

### 5. Inter-Sprint Gates

After each sprint completes, verify:

- **main branch stability**: CI green
- **No unmerged PRs**: All previous sprint PRs merged
- **Worktree cleanup**: Previous sprint worktrees deleted
- **Carryover issues**: If unfinished issues exist, ask user to carryover or cancel

### 6. Final Report

On all sprints complete, output full summary:

```
All sprints complete!

| Sprint | Issues | PRs | Bug Fixes | Status |
|--------|--------|-----|-----------|--------|
| Sprint {N} | {done}/{total} | #{...} | {N} | Done |
| Sprint {N+1} | {done}/{total} | #{...} | {N} | Done |
| ... | ... | ... | ... | ... |

Total issues: {N} completed
Total PRs: {N} merged
Total bugs: {N} fixed
```

---

## Interruption and Resume

On interruption, record current state in MEMORY.md:
- Last completed sprint
- Current in-progress sprint + Phase
- Incomplete work

Resume: `/sprint:all {interrupted_sprint_number}` or `/sprint:cycle {N} phase{M}` to resume from a specific Phase.

Files: 1

Size: 3.0 KB

Complexity: 5/100

Category: General

Source: https://github.com/themagictower/grimoires/tree/main/plugin-sprint/skills/all

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts