quantumbitcz/forge-sprint
skills/forge-sprint/SKILL.md
[writes] Execute multiple features in parallel via sprint orchestration. Use when you have multiple independent features to build, a Linear sprint cycle to execute, or when you want parallel pipeline runs for faster delivery.
development
Updated Apr 20, 2026
$ install --global
skillsauthnpx skillsauth add quantumbitcz/dev-pipeline forge-sprintInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 20, 2026, 5:17 AM5.9s1 file scanned
SKILL.md
- name:
- forge-sprint
- description:
- [writes] Execute multiple features in parallel via sprint orchestration. Use when you have multiple independent features to build, a Linear sprint cycle to execute, or when you want parallel pipeline runs for faster delivery.
- ui:
- { ask: true, tasks: true }
/forge-sprint -- Sprint Execution
Dispatch the sprint orchestrator to analyze and execute multiple features in parallel.
Flags
- --help: print usage and exit 0
- --dry-run: preview actions without writing
Exit codes
See shared/skill-contract.md for the standard exit-code table.
Prerequisites
Before any action, verify:
- Git repository: Run
git rev-parse --show-toplevel 2>/dev/null. If fails: report "Not a git repository. Navigate to a project directory." and STOP. - Forge initialized: Check
.claude/forge.local.mdexists. If not: report "Forge not initialized. Run /forge-init first." and STOP. - No active sprint: Check
.forge/sprint-state.jsonforstatus != complete|failed. If active sprint found, offer resume via AskUserQuestion: "Active sprint found ({sprint_id}, {N} features, {status}). Resume / Start fresh / Abort" - Forge directory: Verify
.forge/directory exists (create if not)
What to Expect
After dispatch, fg-090-sprint-orchestrator will:
- Analyze features for independence (can they run in parallel?)
- Create isolated worktrees per feature
- Run parallel pipeline instances (one per feature)
- Merge results and create PRs
Total time: 15-60 minutes depending on feature count and complexity. Features with shared file conflicts run sequentially.
Instructions
Usage
/forge-sprint -- reads current active Linear cycle
/forge-sprint CYC-42 -- reads specific Linear cycle
/forge-sprint "Feature A" "Feature B" -- manual feature list
Dispatch
dispatch fg-090-sprint-orchestrator "$ARGUMENTS"
The sprint orchestrator handles everything from here -- gathering features, analyzing independence, getting user approval, dispatching pipelines, and coordinating merges.
Resume Mode
If $ARGUMENTS contains --resume or the pre-flight check found an active sprint:
dispatch fg-090-sprint-orchestrator "--resume"
The sprint orchestrator reads .forge/sprint-state.json and resumes from where it left off.
Error Handling
| Condition | Action |
|-----------|--------|
| Prerequisites fail | Report specific error message and STOP |
| No features provided and Linear unavailable | Ask user to provide features manually: /forge-sprint "Feature A" "Feature B" |
| Sprint orchestrator dispatch fails | Report "Sprint orchestrator failed to start. Check plugin installation." and STOP |
| Active sprint conflict | Offer resume, fresh start, or abort via AskUserQuestion |
| Individual feature pipeline fails | Sprint orchestrator handles per-feature failure. Failed features do not block others |
| State corruption | Suggest /forge-recover repair for state.json issues, or /forge-recover reset to start fresh |
See Also
/forge-run-- Run a single feature (use--sprintflag for quick parallel dispatch)/forge-shape-- Shape vague features into structured specs before sprinting/forge-status-- Check progress of active sprint runs/forge-abort-- Stop an active sprint gracefully
Related Skills
quantumbitcz/forge
development
VerifiedTrustedCommunity
[writes] Build, fix, deploy, review, or modify code in this project. Universal entry for the forge pipeline. Auto-bootstraps on first run; brainstorms before planning when given a feature description. Use when you want to take any productive action: implementing features, fixing bugs, reviewing branches, deploying, committing, running migrations.
SKILL.mdUpdated Apr 30, 2026
quantumbitcz/forge-admin
tools
VerifiedTrustedCommunity
[writes] Manage forge state and configuration: recovery, abort, config edits, session handoff, automations, playbooks, output compression, knowledge graph maintenance. Use when you need to recover from broken pipeline state, edit settings, or manage long-lived state.
SKILL.mdUpdated Apr 30, 2026
quantumbitcz/forge-handoff
development
VerifiedTrustedCommunity
[writes] Create, list, show, resume, or search forge session handoffs. Use when context is getting heavy and you want to transfer a forge run or conversation into a fresh Claude Code session, or to resume from a prior handoff artefact. Subcommands - no args (write), list, show, resume, search.
SKILL.mdUpdated Apr 23, 2026
quantumbitcz/forge-graph
development
VerifiedTrustedCommunity
[writes] Manage the Neo4j knowledge graph. Subcommands: init, rebuild (writes); status, query <cypher>, debug (read-only). Requires Docker. No default — an explicit subcommand is required. Use when setting up the graph for the first time, rebuilding after major refactors, checking graph health, or running ad-hoc Cypher diagnostics.
SKILL.mdUpdated Apr 21, 2026