New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Sprint

by Houseofmvps in Houseofmvps/ultraship

Sprint workflow pipeline — chains plan → build → test → review → ship skills into a structured sprint.

MITAuto-check passedAgent Workflows

Install Sprint

skills CLI
$ npx skills add Houseofmvps/ultraship --skill sprint -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Houseofmvps/ultraship sprint --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Houseofmvps/ultraship.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/sprint .claude/skills/sprint && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
sprint
GitHub stars
123
Token cost
~1.4k tokens
SKILL.md length
629 words
Files
1
Skills in repo
28
Repo updated
First seen
Licence
MIT

At a glance

Sprint workflow pipeline — chains plan → build → test → review → ship skills into a structured sprint.

  • Works in 6 steps: Plan → Build → Test → …
  • Starting a new feature
  • SKILL.md covers The Pipeline, Phase 1: Plan, Phase 2: Build and Phase 3: Test, plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Sprint is an agent skill from Houseofmvps/ultraship. Sprint workflow pipeline — chains plan → build → test → review → ship skills into a structured sprint. Use when starting a new feature or project iteration to follow the full lifecycle.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows. The repository describes itself as: "ULTRASHIP" Claude Code plugin — 39 skills, 33 tools, 11 agents for ship-ready workflows: planning, review, pentesting, safety guardrails, canary monitoring, SEO/AI-readiness… The licence is MIT.

When your agent uses it

  • Starting a new feature
  • Project iteration to follow the full lifecycle

Example prompts

  • “/sprint”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Plan
  2. Build
  3. Test
  4. Review
  5. Ship
  6. Verify

What it can do on your machine

Read from SKILL.md and the folder at commit ed232cb. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Sprint loads about 1.4k tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 629 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~48
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Houseofmvps/ultraship at commit ed232cb, republished under its MIT licence (© Houseofmvps). 629 words, ~1,425 tokens.

Download SKILL.mdSave it as .claude/skills/sprint/SKILL.md (or your agent's skills folder).
name
sprint
description
Sprint workflow pipeline — chains plan → build → test → review → ship skills into a structured sprint. Use when starting a new feature or project iteration to follow the full lifecycle.
argument-hint
<feature-description>

Sprint Workflow Pipeline

A sprint is the full lifecycle of shipping a feature — from planning through deployment. This skill chains Ultraship skills into a structured pipeline where each phase produces artifacts that feed the next.

Announce at start: "I'm using the sprint workflow to guide this feature from plan to ship."

The Pipeline

┌──────────┐    ┌──────────┐    ┌──────────┐    ┌──────────┐    ┌──────────┐    ┌──────────┐
│  PLAN    │───▶│  BUILD   │───▶│  TEST    │───▶│  REVIEW  │───▶│  SHIP    │───▶│  VERIFY  │
│          │    │          │    │          │    │          │    │          │    │          │
│ /write-  │    │ /execute-│    │ /tdd     │    │ /review  │    │ /deploy  │    │ /canary  │
│  plan    │    │  plan    │    │          │    │          │    │ /ship    │    │ /retro   │
└──────────┘    └──────────┘    └──────────┘    └──────────┘    └──────────┘    └──────────┘
     │                │               │               │               │               │
     ▼                ▼               ▼               ▼               ▼               ▼
  Plan doc       Working code    Tests pass     Issues fixed    Deployed         Verified

Phase 1: Plan

Trigger: User describes a feature, requirement, or bug to fix.

  1. If the scope is large, use ultraship:brainstorming first to explore the idea space
  2. Use ultraship:writing-plans to create an implementation plan
  3. Plan is saved to docs/ultraship/plans/YYYY-MM-DD-<feature>.md

Artifacts produced: Implementation plan with file map, task list, test strategy

Gate: Plan must be reviewed and approved by user before proceeding to Build.

Phase 2: Build

Trigger: Plan is approved.

  1. Use ultraship:executing-plans to implement the plan task by task
  2. If tasks are independent, use ultraship:dispatching-parallel-agents for parallel execution
  3. If working in isolation, use ultraship:using-git-worktrees for a clean workspace

Scaling to large work: Subagents can now nest up to 5 levels deep — a dispatched implementer can fan out its own helpers for sub-steps. For codebase-wide changes (a migration, a cross-cutting refactor, an audit of every route), prefer a dynamic Workflow: describe the task naturally and include the word "workflow" so Claude generates an orchestration script that pipelines the work across many background subagents with verification built in. Use a single controller for a handful of tasks; escalate to a Workflow when the work-list is large or unknown in size.

Artifacts produced: Working code, committed to a feature branch

Gate: All planned tasks are implemented. Code compiles/runs without errors.

Phase 3: Test

Trigger: Implementation is complete.

  1. Use ultraship:test-driven-development to write tests for new code
  2. Run the full test suite to catch regressions
  3. If bugs are found, use ultraship:systematic-debugging to diagnose (not guess-and-fix)

Artifacts produced: Passing test suite, test coverage for new code

Gate: All tests pass. No known bugs in new code.

Phase 4: Review

Trigger: Tests pass.

  1. Use ultraship:requesting-code-review for self-review
  2. Run /review for automated code review with confidence scoring
  3. Run /secure for security scanning
  4. Fix any high-confidence issues found

Artifacts produced: Review report, security scan results, fixes committed

Gate: No critical or high-severity issues remaining.

Show full SKILL.md (259 more words)Show less

Phase 5: Ship

Trigger: Review is clean.

  1. Use ultraship:verification-before-completion for final verification
  2. Run /ship for the full pre-deploy scorecard (SEO, security, code quality, bundle)
  3. If score is acceptable, run /deploy for the deploy pipeline
  4. Use ultraship:finishing-a-development-branch to merge/PR

Artifacts produced: Deploy to production, PR/merge to main

Gate: /ship scorecard is READY TO SHIP. Deploy succeeds.

Phase 6: Verify

Trigger: Deploy completes.

  1. Run /canary to verify production health
  2. If canary detects issues, escalate to /rescue
  3. Save any deployment learnings via /learn
  4. Run /retro at the end of the sprint to review overall progress

Artifacts produced: Canary report, learnings, retrospective

Workflow Rules

  1. Never skip phases. Each phase exists because skipping it causes problems.
  2. Gates are mandatory. Don't proceed to the next phase until the gate criteria are met.
  3. Artifacts chain forward. Each phase's output is the next phase's input.
  4. The user decides pace. Some sprints complete in an hour. Some take a week. The pipeline adapts.
  5. Small batches. Prefer shipping small features frequently over large features infrequently.

Quick Sprint (for small changes)

For bug fixes or small features (< 50 lines of code), compress the pipeline:

  1. Investigate → Use /investigate to find root cause
  2. Fix + Test → Fix the bug, write a test
  3. Verify → Run /review, check tests pass
  4. Ship → Push and run /canary

Skip the full planning phase for changes that don't need it.

Sprint Status

Track sprint progress using tasks. At any point, the user can ask "where are we?" and get a clear answer:

Sprint: Add webhook retry logic
Phase: 3/6 — TEST
Status: 2 tests written, 1 failing (timeout issue in retry delay)
Next: Fix failing test, then proceed to REVIEW

© Houseofmvps, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/sprint of Houseofmvps/ultraship.

Open the folder on GitHubat commit ed232cb

Compare with similar skills

Sprint next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Sprint compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Sprint this skillHouseofmvps/ultraship123—~1.4kAutomated safety check: PassMIT
Diagnosing Superpowers Sessionsobra/superpowers297k3 repos~1.7kAutomated safety check: PassMIT
Grillingpietheinstrengholt/rssmonster56431 repos~510Automated safety check: PassMIT
CodeGraph Agent Evalcolbymchenry/codegraph74k—~950Automated safety check: PassMIT
Improvefossasia/eventyay-interpretation1.6k10 repos~3.7kAutomated safety check: WarnMIT
Kayba Stage 1 API Analysiskayba-ai/agentic-context-engine2.6k—~1.1kAutomated safety check: PassApache-2.0

Similar skills

  • Diagnosing Superpowers Sessions

    obra/superpowers

    Investigates a session where Superpowers went wrong, reads the transcripts on disk and produces an evidence-cited report, optionally prepared as a bug report for the maintainers.

    297k GitHub starsUsed in 3 repos~1.7k tokens
    Agent WorkflowsAuto-check passed

  • Grilling

    pietheinstrengholt/rssmonster

    Grill the user relentlessly about a plan, decision, or idea.

    564 GitHub starsUsed in 31 repos~510 tokens
    Agent WorkflowsAuto-check passed

  • CodeGraph Agent Eval

    colbymchenry/codegraph

    Benchmarks how much CodeGraph helps a coding agent on a real repository, comparing runs with and without it for a chosen local or published version.

    74k GitHub stars~950 tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

  • Improve

    fossasia/eventyay-interpretation

    Survey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute.

    1.6k GitHub starsUsed in 10 repos~3.7k tokens
    Agent WorkflowsAuto-check: warnings

  • Kayba Stage 1 API Analysis

    kayba-ai/agentic-context-engine

    Fetch pre-computed insights from the Kayba API and build a structured summary.

    2.6k GitHub stars~1.1k tokensUpdated 15 days ago
    Agent WorkflowsAuto-check passed

  • Agent QA Authoring

    vostride/agent-qa

    A skill your agent uses when creating, editing, validating, or running agent-qa tests, suites, or hooks.

    903 GitHub stars~569 tokensUpdated 2 mo ago
    Agent WorkflowsAuto-check passed

More from Houseofmvps/ultraship

All 28 skills in this repo

  • Using Ultraship

    Houseofmvps/ultraship

    A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

    123 GitHub stars~2.2k tokensUpdated 3 mo ago
    Auto-check passed

  • A11y

    Houseofmvps/ultraship

    Accessibility audit + auto-fix (WCAG 2.2 A/AA). An agent skill from Houseofmvps/ultraship.

    123 GitHub stars~1.2k tokensUpdated 3 mo ago
    Auto-check: notes

  • Architecture

    Houseofmvps/ultraship

    Living Architecture Map — auto-generate Mermaid diagrams of your codebase.

    123 GitHub stars~708 tokensUpdated 3 mo ago
    Auto-check: notes

  • Clone Patterns

    Houseofmvps/ultraship

    Learn From the Best — analyze patterns from any codebase and apply them to yours.

    123 GitHub stars~682 tokensUpdated 3 mo ago
    Auto-check: notes

  • Code Review

    Houseofmvps/ultraship

    Code review with principal-engineer-level depth. An agent skill from Houseofmvps/ultraship.

    123 GitHub stars~1.5k tokensUpdated 3 mo ago
    Auto-check passed

  • Compete

    Houseofmvps/ultraship

    Competitive X-Ray — analyze any competitor URL vs your site.

    123 GitHub stars~1.1k tokensUpdated 3 mo ago
    Auto-check: notes

Categories

Questions about Sprint

What does Sprint do?

Sprint workflow pipeline — chains plan → build → test → review → ship skills into a structured sprint. Sprint is an agent skill from Houseofmvps/ultraship. Sprint workflow pipeline — chains plan → build → test → review → ship skills into a structured sprint.

When should I use Sprint?

Sprint fits situations like: starting a new feature; project iteration to follow the full lifecycle.

How do I install Sprint in Claude Code?

Run `npx skills add Houseofmvps/ultraship --skill sprint -a claude-code`. Or copy the skill folder (skills/sprint in Houseofmvps/ultraship) into .claude/skills/sprint in your project. Claude Code loads it when a task matches its description.

How do I install Sprint in Codex?

Run `npx skills add Houseofmvps/ultraship --skill sprint -a codex`. Or copy the skill folder (skills/sprint in Houseofmvps/ultraship) into .agents/skills/sprint in your project. Codex loads it when a task matches its description.

Can I use Sprint in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Houseofmvps/ultraship --skill sprint -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sprint, .gemini/skills/sprint, .github/skills/sprint and .opencode/skills/sprint in your project.

What does Sprint need to run?

SKILL.md names no scripts, command-line tools or credentials: Sprint is instructions for the agent only.

Does Sprint access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Sprint safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Sprint use?

Sprint is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Sprint use?

About 1.4k tokens (SKILL.md is roughly 5.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Sprint?

Skills that share tags, products or a category with Sprint: Diagnosing Superpowers Sessions (obra/superpowers, 297k stars), Grilling (pietheinstrengholt/rssmonster, 564 stars), CodeGraph Agent Eval (colbymchenry/codegraph, 74k stars) and Improve (fossasia/eventyay-interpretation, 1.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Sprint?

Houseofmvps (a GitHub user) maintains it in Houseofmvps/ultraship, which has 123 GitHub stars. The repository holds 28 skills in this directory. The repository was last updated on July 8, 2026.

Source: Houseofmvps/ultraship on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.