Agent skill

Feature Sprint

by PackmindHub in PackmindHub/packmind

Execute the implementation plan produced by /feature-spec. An agent skill from PackmindHub/packmind.

Apache-2.0Auto-check passedAgent Workflows

Install Feature Sprint

skills CLI
$ npx skills add PackmindHub/packmind --skill feature-sprint -a claude-code

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

GitHub CLI
$ gh skill install PackmindHub/packmind feature-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/PackmindHub/packmind.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/feature-sprint .claude/skills/feature-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
feature-sprint
GitHub stars
317
Token cost
~1.9k tokens
SKILL.md length
572 words
Files
8 (incl. scripts, references)
Skills in repo
35
Repo updated
First seen
Licence
Apache-2.0

At a glance

Execute the implementation plan produced by /feature-spec. An agent skill from PackmindHub/packmind.

  • Works in 4 steps: Read implementation-plan.md → extract… → Read context.md → extract… → Use TaskCreate for each pending task… → …
  • Tasks that involve PRD writing
  • SKILL.md covers When to Use, Prerequisites, Architecture: Orchestration +… and Workflow Phases, plus 7 more sections
  • Runs Python scripts from its folder; calls git

What it does

Feature Sprint is an agent skill from PackmindHub/packmind. Execute the implementation plan produced by /feature-spec. Loads tasks from tmp/feature-specs/{slug}/implementation-plan.md, hydrates them as Claude Tasks, runs parallel groups via subagents in the correct repo (OSS sibling at ../packmind or the proprietary repo in cwd), syncs progress back to checkboxes, commits per group, and runs Nx quality gates. Resumable across sessions via checkbox state.

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files, including scripts and reference files (for example `phase-1-init.md`, `phase-2-execute.md` and `phase-3-finalize.md`).

It sits in Agent Workflows, covering PRD writing, Planning and Subagents. The repository describes itself as: Packmind seamlessly captures your engineering playbook and turns it into AI context, guardrails, and governance. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve PRD writing
  • Tasks that involve Planning
  • Tasks that involve Subagents

Example prompts

  • “/feature-sprint”

Requirements

  • Python 3

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Read implementation-plan.md → extract tasks with checkbox state ([ ] pending, [x] done)
  2. Read context.md → extract parallel_groups, target_repo, quality_gates
  3. Use TaskCreate for each pending task (visual tracking)
  4. Wire addBlockedBy from parallel_groups[*].blocked_by

What it can do on your machine

Read from SKILL.md and the folder at commit 8a10541. 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

    Ships 3 files in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • git

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

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    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

Feature Sprint loads about 1.9k tokens when it runs, and up to ~2.9k if it reads all its reference files. Until then it costs about 103 tokens; SKILL.md has 572 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~103
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.9k

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); the scripts in this folder are not scanned.

SKILL.md

The full file from PackmindHub/packmind at commit 8a10541, republished under its Apache-2.0 licence (© PackmindHub). 572 words, ~1,891 tokens.

Download SKILL.mdSave it as .claude/skills/feature-sprint/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.
name
feature-sprint
description
Execute the implementation plan produced by /feature-spec. Loads tasks from tmp/feature-specs/{slug}/implementation-plan.md, hydrates them as Claude Tasks, runs parallel groups via subagents in the correct repo (OSS sibling at ../packmind or the proprietary repo in cwd), syncs progress back to checkboxes, commits per group, and runs Nx quality gates. Resumable across sessions via checkbox state.

Feature Sprint Skill

Execute a Packmind feature implementation plan via subagents with automatic parallel execution and sync-back. Companion to /feature-spec.

When to Use

ScenarioUse feature-sprintUse plan + architect-executor
Fast execution of an already-specified feature✅❌
Parallel group execution✅partial
Multi-repo (OSS + proprietary) execution✅❌
Heavy TDD enforcement, per-task escalation❌✅
Specs in tmp/feature-specs/ (this flow)✅❌
Specs in .claude/specs/ and .claude/plans/❌✅

Rule of thumb: /feature-sprint is the executor for /feature-spec. For more careful, single-task-at-a-time execution with the global plan skill, use architect-executor instead.

Prerequisites

A completed feature spec at tmp/feature-specs/{slug}/:

  • {slug}.md with status: COMPLETE in frontmatter
  • context.md with YAML frontmatter (version 1.0+)
  • implementation-plan.md with task checkboxes

If missing or DRAFT: tell the user to run /feature-spec {source} first.

Architecture: Orchestration + Subagents + Sync-Back

Core Principle: The main session orchestrates only. All implementation happens in Task subagents — that keeps the main context clean and lets agents do heavy reading without poisoning your conversation.

┌─────────────────────────────────────────────────────────────────┐
│  Persistent Layer (tmp/, git-ignored)                            │
│  ┌─────────────────────────────────────────────────────────────┐ │
│  │ implementation-plan.md                                      │ │
│  │ Source of truth: task checkboxes [ ] / [x]                  │ │
│  └─────────────────────────────────────────────────────────────┘ │
└─────────────────────────────────────────────────────────────────┘
         │                              ▲
         │ Hydrate (session start)      │ Sync-back (per group)
         ▼                              │
┌─────────────────────────────────────────────────────────────────┐
│  Main Session (ORCHESTRATION ONLY)                               │
│  • Load spec & state         • Spawn subagents (one per group)  │
│  • Parse agent output        • Sync checkboxes                  │
│  • Run Nx quality gates      • Commit per group                 │
│  • NEVER implement tasks directly                                │
└─────────────────────────────────────────────────────────────────┘
                              │
                              │ Spawn (parallel or sequential)
                              ▼
┌─────────────────────────────────────────────────────────────────┐
│  Subagent Layer (IMPLEMENTATION)                                 │
│  ┌────────────────┐  ┌────────────────┐  ┌────────────────────┐ │
│  │ Group A agent  │  │ Group B agent  │  │ Group C agent      │ │
│  │ Backend tasks  │  │ Frontend tasks │  │ Tests / integration│ │
│  │ cwd: OSS repo  │  │ cwd: OSS repo  │  │ cwd: depends       │ │
│  └────────────────┘  └────────────────┘  └────────────────────┘ │
└─────────────────────────────────────────────────────────────────┘
Hydration (session start)
  1. Read implementation-plan.md → extract tasks with checkbox state ([ ] pending, [x] done)
  2. Read context.md → extract parallel_groups, target_repo, quality_gates
  3. Use TaskCreate for each pending task (visual tracking)
  4. Wire addBlockedBy from parallel_groups[*].blocked_by
Subagent delegation

Every group runs in a Task subagent — parallel or sequential. The main session never touches code, never reads source files, never runs Nx commands itself.

Sync-back (automatic)

After each group's subagent completes:

  1. Parse output for TASK_COMPLETE: {id} markers
  2. Update implementation-plan.md checkboxes: [ ] → [x]
  3. Update Claude Tasks status

Progress is durable: kill the session, restart /feature-sprint {slug}, and it resumes from where checkboxes left off.

Workflow Phases

PhaseFilePurpose
1phase-1-init.mdLoad spec, hydrate tasks, get approval
2phase-2-execute.mdParallel execution via subagents with auto sync-back + per-group commits
3phase-3-finalize.mdRun Nx quality gates, final report, optional archive

State Management

tmp/feature-specs/{slug}/
├── {slug}.md              # status: COMPLETE
├── context.md             # parallel_groups, target_repo, quality_gates
├── implementation-plan.md # tasks with checkboxes — SOURCE OF TRUTH for progress
├── discovery.md           # reference patterns
└── functional-spec.md     # acceptance criteria

Progress is tracked entirely through implementation-plan.md checkboxes — no separate state file.

OSS / Proprietary Routing

context.md declares target_repo and each parallel group declares its repo field. The main session sets cwd for each subagent accordingly:

  • repo: oss → cwd: ../packmind (the OSS sibling cloned next to the proprietary repo)
  • repo: proprietary → cwd: . (this repo)

After all OSS work is committed and merged upstream, remind the user to git pull here so the proprietary fork picks up the auto-merge before any proprietary tasks run.

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

Commit Strategy

Each parallel group gets its own commit when its subagent reports success (one commit per group, not per task). This matches the Packmind CLAUDE.md rule "Each sub-task should have its own commit" — we treat a parallel group as a coherent sub-task unit.

Commits follow the git-commit-guidelines skill format (gitmoji + Conventional Commits, never auto-closing issues). The main session always shows the proposed message and asks for approval before running git commit.

Invocation

New sprint
/feature-sprint {task_slug}

If {task_slug} is omitted, the skill lists available specs in tmp/feature-specs/ and asks the user to pick one.

Resume

Same command. The skill detects existing checkbox state and offers to continue.

Status

Show progress across active sprints:

/feature-sprint status

(Implemented by listing tmp/feature-specs/*/implementation-plan.md and counting checkbox state in each.)

Error Handling

SituationAction
Spec not foundError: "Run /feature-spec first"
Spec DRAFTError: "Complete the spec first — status is DRAFT"
No parallel groupsFall back to single-group sequential execution
repo: oss but ../packmind missingAsk user — switch to proprietary or abort
Agent failsSync completed tasks, pause sprint, report error
Quality gate failsSync progress, report failures, prompt for fix-and-retry

Integration with /feature-spec

/feature-spec #123              # produces tmp/feature-specs/{slug}/
/feature-sprint {slug}          # executes the plan

Sprint reads:

  • context.md → parallel_groups, target_repo, quality_gates
  • implementation-plan.md → task list with checkboxes (source of truth)
  • {slug}.md → verify status: COMPLETE

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

Files

SKILL.md and 7 other files (scripts, references) in .agents/skills/feature-sprint of PackmindHub/packmind.

  • SKILL.md
  • phase-1-init.md
  • phase-2-execute.md
  • phase-3-finalize.md
  • references/group-prompt-template.md
  • scripts/parse_implementation_plan.py
  • scripts/resolve_ready_groups.py
  • scripts/sync_checkboxes.py

Open the folder on GitHubat commit 8a10541

Compare with similar skills

Feature 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.

Feature Sprint compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Feature Sprint this skillPackmindHub/packmind317—~1.9kAutomated safety check: PassApache-2.0
Workflow Orchestrationvxcozy/workflow-orchestration116—~1kAutomated safety check: PassMIT
Execute Taskanombyte93/prd-taskmaster604—~4.8kAutomated safety check: NotesMIT
Subagent Driven DevelopmentNeoLabHQ/context-engineering-kit1.7k—~2.8kAutomated safety check: PassGPL-3.0
Subagent Driven Developmentaiskillstore/marketplace4301 repos~1.3kAutomated safety check: PassNone
Subagent Driven DevelopmentAsvarox/allkaraoke26138 repos~1.2kAutomated safety check: PassNone

Similar skills

  • Workflow Orchestration

    vxcozy/workflow-orchestration

    Disciplined task execution with planning, verification, and self-improvement loops.

    116 GitHub stars~1k tokensUpdated 5 mo ago
    Agent WorkflowsAuto-check passed
  • Execute Task

    anombyte93/prd-taskmaster

    Execute the next TaskMaster task using the implementation plan with CDD verification.

    604 GitHub stars~4.8k tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check: notes
  • Subagent Driven Development

    NeoLabHQ/context-engineering-kit

    A skill your agent uses when executing implementation plans with independent tasks in the current session or facing 3+ independent issues that can be investigated without shared state or…

    1.7k GitHub stars~2.8k tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check passed
  • Subagent Driven Development

    aiskillstore/marketplace

    A skill your agent uses when executing implementation plans with independent tasks in the current session - dispatches fresh subagent for each task with code review between tasks, enabling fast…

    430 GitHub starsUsed in 1 repo~1.3k tokens
    Agent WorkflowsAuto-check passed
  • Subagent Driven Development

    Asvarox/allkaraoke

    A skill your agent uses when executing implementation plans with independent tasks in the current session

    261 GitHub starsUsed in 38 repos~1.2k tokens
    Agent WorkflowsAuto-check passed
  • Exec

    umputun/cc-thingz

    Execute plan tasks sequentially using subagents. An agent skill from umputun/cc-thingz.

    484 GitHub stars~8k tokensUpdated 3 days ago
    Agent WorkflowsAuto-check passed

More from PackmindHub/packmind

All 35 skills in this repo
  • Michel CLI Demo Recorder

    PackmindHub/packmind

    Produce proof-of-execution demos of the Packmind CLI (packmind-cli) as terminal-styled images (colors and formatting preserved exactly), for embedding in a GitHub PR.

    317 GitHub stars~3.4k tokensUpdated today
    Auto-check passed
  • Michel UI Demo Recorder

    PackmindHub/packmind

    Record polished UI demo videos and screenshots of a running web app using Playwright MCP — for client deliverables, release notes, feature walkthroughs, or bug repros.

    317 GitHub stars~6.4k tokensUpdated today
    Auto-check passed
  • Packmind Create Skill

    PackmindHub/packmind

    Guide for creating effective skills. An agent skill from PackmindHub/packmind.

    317 GitHub stars~3.5k tokensUpdated today
    Auto-check: notes
  • Doc Audit

    PackmindHub/packmind

    Audit Packmind end-user documentation (apps/doc/) for broken links, outdated CLI references, non-existent concepts, misleading information, and missing coverage.

    317 GitHub stars~2.4k tokensUpdated today
    Auto-check passed
  • Review an implemented GitHub issue the way a senior Packmind engineer would — the human-judgment checks that ESLint, the TypeScript compiler, and e2e tests cannot catch (authorization scoping…

    317 GitHub stars~2.7k tokensUpdated today
    Auto-check passed
  • Packmind Update Playbook

    PackmindHub/packmind

    A skill your agent uses when updating, adding, fixing, changing, or deprecating Packmind playbook artifacts (standards, commands, skills).

    317 GitHub stars~1.9k tokensUpdated today
    Auto-check passed

Categories

Questions about Feature Sprint

What does Feature Sprint do?

Execute the implementation plan produced by /feature-spec. An agent skill from PackmindHub/packmind. Feature Sprint is an agent skill from PackmindHub/packmind. Execute the implementation plan produced by /feature-spec.

When should I use Feature Sprint?

Feature Sprint fits situations like: tasks that involve PRD writing; tasks that involve Planning; tasks that involve Subagents.

How do I install Feature Sprint in Claude Code?

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

How do I install Feature Sprint in Codex?

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

Can I use Feature 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 PackmindHub/packmind --skill feature-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/feature-sprint, .gemini/skills/feature-sprint, .github/skills/feature-sprint and .opencode/skills/feature-sprint in your project.

What does Feature Sprint need to run?

Going by SKILL.md and its folder, Feature Sprint needs Python for the scripts in its folder and the command-line tools its instructions call (git). Our summary lists: Python 3.

Does Feature Sprint access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Feature 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Feature Sprint use?

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

How many tokens does Feature Sprint use?

About 1.9k tokens (SKILL.md is roughly 7.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 988 tokens, read only when the agent opens those files.

What are the alternatives to Feature Sprint?

Skills that share tags, products or a category with Feature Sprint: Workflow Orchestration (vxcozy/workflow-orchestration, 116 stars), Execute Task (anombyte93/prd-taskmaster, 604 stars), Subagent Driven Development (NeoLabHQ/context-engineering-kit, 1.7k stars) and Subagent Driven Development (aiskillstore/marketplace, 430 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Feature Sprint?

PackmindHub (a GitHub organization) maintains it in PackmindHub/packmind, which has 317 GitHub stars. The repository holds 35 skills in this directory. The repository was last updated on October 8, 2026.

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