메뉴
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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| 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> |
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."
┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐
│ 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
Trigger: User describes a feature, requirement, or bug to fix.
ultraship:brainstorming first to explore the idea spaceultraship:writing-plans to create an implementation plandocs/ultraship/plans/YYYY-MM-DD-<feature>.mdArtifacts produced: Implementation plan with file map, task list, test strategy
Gate: Plan must be reviewed and approved by user before proceeding to Build.
Trigger: Plan is approved.
ultraship:executing-plans to implement the plan task by taskultraship:dispatching-parallel-agents for parallel executionultraship:using-git-worktrees for a clean workspaceScaling 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.
Trigger: Implementation is complete.
ultraship:test-driven-development to write tests for new codeultraship: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.
Trigger: Tests pass.
ultraship:requesting-code-review for self-review/review for automated code review with confidence scoring/secure for security scanningArtifacts produced: Review report, security scan results, fixes committed
Gate: No critical or high-severity issues remaining.
Trigger: Review is clean.
ultraship:verification-before-completion for final verification/ship for the full pre-deploy scorecard (SEO, security, code quality, bundle)/deploy for the deploy pipelineultraship:finishing-a-development-branch to merge/PRArtifacts produced: Deploy to production, PR/merge to main
Gate: /ship scorecard is READY TO SHIP. Deploy succeeds.
Trigger: Deploy completes.
/canary to verify production health/rescue/learn/retro at the end of the sprint to review overall progressArtifacts produced: Canary report, learnings, retrospective
For bug fixes or small features (< 50 lines of code), compress the pipeline:
/investigate to find root cause/review, check tests pass/canarySkip the full planning phase for changes that don't need it.
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
Build a regression + eval harness for AI-written code and AI features. Generates characterization tests that lock current behavior before a refactor, scaffolds a Promptfoo eval suite for chatbots/RAG/classifiers, and wires it into the ship-gate. Use when the user wants evals, regression tests for AI code, to stop AI features drifting, or to test an LLM feature.
Run security audit — dependency vulnerabilities, secret scanning, OWASP pattern detection, HTTP headers. Use when user wants to harden their project.
Accessibility audit + auto-fix (WCAG 2.2 A/AA). Scans built/static HTML for screen-reader, keyboard, and structure failures, fixes the deterministic ones, and escalates to a rendered scan for contrast and focus. Use when the user wants to check or improve accessibility, fix WCAG issues, or pass an a11y review.
Turn the /ship scorecard into a blocking, config-as-code quality gate. Sets per-category score thresholds, hard-fails on leaked secrets or critical findings, and wires the gate into a pre-push hook and CI so nothing below the bar merges. Use when the user wants a merge gate, CI quality gate, pre-push check, or to enforce ship-readiness.
Post-deploy canary monitoring — checks site health, detects regressions, monitors for errors after deployment. Use after deploying to verify production is healthy.
Code review with principal-engineer-level depth. Reviews for correctness, performance, security, maintainability, and architecture. Use when completing tasks, reviewing PRs, or before merging.