Workflow Orchestration
vxcozy/workflow-orchestration
Disciplined task execution with planning, verification, and self-improvement loops.
Execute the implementation plan produced by /feature-spec. An agent skill from PackmindHub/packmind.
$ npx skills add PackmindHub/packmind --skill feature-sprint -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install PackmindHub/packmind feature-sprint --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "feature-sprint" agent skill from https://github.com/PackmindHub/packmind/tree/main/.agents/skills/feature-sprint into .claude/skills/feature-sprint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feature-sprint", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/PackmindHub/packmind/tree/main/.agents/skills/feature-sprintType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add PackmindHub/packmind --skill feature-sprint -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install PackmindHub/packmind feature-sprint --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PackmindHub/packmind.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/feature-sprint .agents/skills/feature-sprint && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "feature-sprint" agent skill from https://github.com/PackmindHub/packmind/tree/main/.agents/skills/feature-sprint into .agents/skills/feature-sprint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feature-sprint", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add PackmindHub/packmind --skill feature-sprint -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install PackmindHub/packmind feature-sprint --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PackmindHub/packmind.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/feature-sprint .cursor/skills/feature-sprint && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "feature-sprint" agent skill from https://github.com/PackmindHub/packmind/tree/main/.agents/skills/feature-sprint into .cursor/skills/feature-sprint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feature-sprint", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/PackmindHub/packmind.git --path .agents/skills/feature-sprint--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add PackmindHub/packmind --skill feature-sprint -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install PackmindHub/packmind feature-sprint --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PackmindHub/packmind.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/feature-sprint .gemini/skills/feature-sprint && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "feature-sprint" agent skill from https://github.com/PackmindHub/packmind/tree/main/.agents/skills/feature-sprint into .gemini/skills/feature-sprint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feature-sprint", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install PackmindHub/packmind feature-sprintInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add PackmindHub/packmind --skill feature-sprint -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/PackmindHub/packmind.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/feature-sprint .github/skills/feature-sprint && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "feature-sprint" agent skill from https://github.com/PackmindHub/packmind/tree/main/.agents/skills/feature-sprint into .github/skills/feature-sprint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feature-sprint", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add PackmindHub/packmind --skill feature-sprint -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install PackmindHub/packmind feature-sprint --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PackmindHub/packmind.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/feature-sprint .opencode/skills/feature-sprint && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "feature-sprint" agent skill from https://github.com/PackmindHub/packmind/tree/main/.agents/skills/feature-sprint into .opencode/skills/feature-sprint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feature-sprint", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
feature-sprintExecute 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. 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.
4 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 8a10541. It shows what the files ask for, not the result of running them.
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.
Ships 3 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
gitFrom the folder's file list and the shell code blocks in SKILL.md.
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.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
The full file from PackmindHub/packmind at commit 8a10541, republished under its Apache-2.0 licence (© PackmindHub). 572 words, ~1,891 tokens.
.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.Execute a Packmind feature implementation plan via subagents with automatic parallel execution and sync-back. Companion to /feature-spec.
| 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.
A completed feature spec at tmp/feature-specs/{slug}/:
{slug}.md with status: COMPLETE in frontmattercontext.md with YAML frontmatter (version 1.0+)implementation-plan.md with task checkboxesIf missing or DRAFT: tell the user to run /feature-spec {source} first.
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 │ │
│ └────────────────┘ └────────────────┘ └────────────────────┘ │
└─────────────────────────────────────────────────────────────────┘implementation-plan.md → extract tasks with checkbox state ([ ] pending, [x] done)context.md → extract parallel_groups, target_repo, quality_gatesTaskCreate for each pending task (visual tracking)addBlockedBy from parallel_groups[*].blocked_byEvery group runs in a Task subagent — parallel or sequential. The main session never touches code, never reads source files, never runs Nx commands itself.
After each group's subagent completes:
TASK_COMPLETE: {id} markersimplementation-plan.md checkboxes: [ ] → [x]Progress is durable: kill the session, restart /feature-sprint {slug}, and it resumes from where checkboxes left off.
| Phase | File | Purpose |
|---|---|---|
| 1 | phase-1-init.md | Load spec, hydrate tasks, get approval |
| 2 | phase-2-execute.md | Parallel execution via subagents with auto sync-back + per-group commits |
| 3 | phase-3-finalize.md | Run Nx quality gates, final report, optional archive |
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 criteriaProgress is tracked entirely through implementation-plan.md checkboxes — no separate state file.
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.
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.
/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.
Same command. The skill detects existing checkbox state and offers to continue.
Show progress across active sprints:
/feature-sprint status(Implemented by listing tmp/feature-specs/*/implementation-plan.md and counting checkbox state in each.)
| Situation | Action |
|---|---|
| Spec not found | Error: "Run /feature-spec first" |
| Spec DRAFT | Error: "Complete the spec first — status is DRAFT" |
| No parallel groups | Fall back to single-group sequential execution |
repo: oss but ../packmind missing | Ask user — switch to proprietary or abort |
| Agent fails | Sync completed tasks, pause sprint, report error |
| Quality gate fails | Sync progress, report failures, prompt for fix-and-retry |
/feature-spec #123 # produces tmp/feature-specs/{slug}/
/feature-sprint {slug} # executes the planSprint reads:
context.md → parallel_groups, target_repo, quality_gatesimplementation-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
SKILL.md and 7 other files (scripts, references) in .agents/skills/feature-sprint of PackmindHub/packmind.
Open the folder on GitHubat commit 8a10541
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Feature Sprint this skillPackmindHub/packmind | 317 | — | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| Workflow Orchestrationvxcozy/workflow-orchestration | 116 | — | ~1k | Automated safety check: Pass | MIT | |
| Execute Taskanombyte93/prd-taskmaster | 604 | — | ~4.8k | Automated safety check: Notes | MIT | |
| Subagent Driven DevelopmentNeoLabHQ/context-engineering-kit | 1.7k | — | ~2.8k | Automated safety check: Pass | GPL-3.0 | |
| Subagent Driven Developmentaiskillstore/marketplace | 430 | 1 repos | ~1.3k | Automated safety check: Pass | None | |
| Subagent Driven DevelopmentAsvarox/allkaraoke | 261 | 38 repos | ~1.2k | Automated safety check: Pass | None |
vxcozy/workflow-orchestration
Disciplined task execution with planning, verification, and self-improvement loops.
anombyte93/prd-taskmaster
Execute the next TaskMaster task using the implementation plan with CDD verification.
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…
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…
Asvarox/allkaraoke
A skill your agent uses when executing implementation plans with independent tasks in the current session
umputun/cc-thingz
Execute plan tasks sequentially using subagents. An agent skill from umputun/cc-thingz.
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.
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.
PackmindHub/packmind
Guide for creating effective skills. An agent skill from PackmindHub/packmind.
PackmindHub/packmind
Audit Packmind end-user documentation (apps/doc/) for broken links, outdated CLI references, non-existent concepts, misleading information, and missing coverage.
PackmindHub/packmind
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…
PackmindHub/packmind
A skill your agent uses when updating, adding, fixing, changing, or deprecating Packmind playbook artifacts (standards, commands, skills).
Categories
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.
Feature Sprint fits situations like: tasks that involve PRD writing; tasks that involve Planning; tasks that involve Subagents.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.