Borrowing it
Nothing to install: this file belongs to PackmindHub/packmind. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/PackmindHub/packmind/main/.agents/skills/feature-sprint/SKILL.mdgit clone --depth 1 https://github.com/PackmindHub/packmindWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/packmindhub/packmind/feature-sprint)<a href="https://agentmods.dev/skills/packmindhub/packmind/feature-sprint"><img src="https://agentmods.dev/badge/skills/packmindhub/packmind/feature-sprint/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/packmindhub/packmind/feature-sprint"><img src="https://agentmods.dev/badge/skills/packmindhub/packmind/feature-sprint.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00087 | $0.01750 |
| Opus 5.5 | $0.00035 | $0.00700 |
| Sonnet 5.5 | $0.00017 | $0.00350 |
| Haiku 4.5 | $0.00009 | $0.00175 |
Grade A, and why
feature-sprint scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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
| Scenario | Use feature-sprint | Use 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}.mdwithstatus: COMPLETEin frontmattercontext.mdwith YAML frontmatter (version 1.0+)implementation-plan.mdwith 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 │ │
│ └────────────────┘ └────────────────┘ └────────────────────┘ │
└─────────────────────────────────────────────────────────────────┘
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 165 lines · 87 tokens per session scan A 5f23490132f5
feature-sprint is a skill published in the GitHub repository PackmindHub/packmind (319 stars, last pushed 4d ago), licensed Apache-2.0. It adds 87 tokens to every session and 1,750 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-22.
Other skills, from other repositories
ce-compound
Document a recently solved problem or durable project vocabulary in docs/solutions/ or CONCEPTS.md. Use when capturing a learning after work.
ce-work
Execute a plan or concrete work prompt end-to-end. Use when implementing from docs/plans, a spec path, or a clear build request; use ce-debug for open-ended bugs.
sdd
Execute the Liatrio Spec-Driven Development (SDD) workflow when explicitly invoked by the user. NOTE: this skill is NOT intended to be dynamically loaded or automatically triggered; it should only ever be explicitly called by the user.
loadout-import-workflow
Import another repo's command/skill suite into loadout as a workflow. Use when the user points at an agent framework, plugin, or command pack (e.g. a GitHub repo, a .claude/commands/ directory, a skills pack) and wants its process turned into a loadout [[workflows]] entry — "import this workflow", "turn this plugin…
ce-commit-push-pr
Commit, push, and open a PR. Use when asked to ship/open a PR, or for PR-description-only flows like writing, rewriting, or describing a PR body.
loadout-migrate
Migrate existing global AI agent instructions into loadout. Use when adopting loadout, importing a CLAUDE.md / AGENTS.md / global agent rules into loadout, setting up /.config/loadout/config.toml, or turning prose agent instructions into reusable fragments and stack-targeted profiles.