sprint-planner

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add skills/vmobifystudio/app-dev-team/sprint-planner

Any agent

npx skills add vmobifystudio/app-dev-team --skill sprint-planner

Clone the repo

git clone --depth 1 https://github.com/vmobifystudio/app-dev-team

Made for: Claude Code, Codex.

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

README.md

[![agentmods](https://agentmods.dev/badge/skills/vmobifystudio/app-dev-team/sprint-planner.svg)](https://agentmods.dev/skills/vmobifystudio/app-dev-team/sprint-planner)

Your own site

<a href="https://agentmods.dev/skills/vmobifystudio/app-dev-team/sprint-planner"><img src="https://agentmods.dev/badge/skills/vmobifystudio/app-dev-team/sprint-planner.svg" alt="Measured on agentmods" height="20"></a>

Per session 53 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,314 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin unknown No closer match found in the catalogue.

Token cost

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	$0.00053	$0.03314
Opus 5	$0.00026	$0.01657
Sonnet 5	$0.00011	$0.00663
Haiku 4.5	$0.00005	$0.00331

Measured today against content hash 7dd98a99e263, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

sprint-planner 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 today.

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.

skills/sprint-planner/SKILL.md · 239 lines

How it starts

The opening of the file, as written. The whole thing — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Sprint planner

Convert docs/11-backlog.md + docs/22-impl-spec-*.md into docs/30-sprint-plan.md and docs/31-board.md.

Procedure

Read the backlog and impl specs. Note ticket dependencies — if APP-002 needs APP-001's auth module, that's a dependency.
Sprint goal — one sentence at the top of docs/30-sprint-plan.md.
Capacity — default 3 developer agents (iOS, Android, optional Backend), 1 code-reviewer, 1 qa-engineer, 1 ux-architect, 1 product-designer. Tune to project scope.

Assign for parallelism — group tickets so each developer has independent work to start with. Stack dependent work behind it.

Track A (ios-developer)  : APP-001 → APP-004 → APP-007
Track B (android-dev)    : APP-002 → APP-005 → APP-008
Track C (backend-dev)    : APP-003 → APP-006
Continuous: code-reviewer, qa-engineer, ux-architect + product-designer (early)

Board — create tickets through the CLI. Never hand-write the table.

docs/31-board.md is a generated view. The source of truth is the append-only event log docs/31-board-events.jsonl, and scripts/board.mjs is its only writer. A ticket is created by:
```
node "${CLAUDE_PLUGIN_ROOT}/scripts/board.mjs" add APP-001 \
  --title "Core todo store" --feature F-001 --owner android-developer \
  --depends APP-000 --estimate M --spec "prd#F-001 + arch§3" \
  --acceptance "Given the list, When I submit non-empty text, Then it appears at the top" \
  --notes "touches: data/TodoRepository.kt"
```
Each add appends a created event and re-renders the Markdown board with the same columns as before — ID | Feature | Title | Owner | Reviewer | Status | Cycles | Depends on | Estimate | Spec | Acceptance | Notes. Editing a cell by hand does nothing: the next render overwrites it, and no rule reads it back. Reviewer and Cycles are derived, not typed — the drift between a hand-edited Cycles cell and the ledger was a live defect, and derived-on-read cannot disagree with itself.

Read the full file on GitHub · 239 lines

Changes

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.

today First seen · 239 lines · 53 tokens per session scan A 7dd98a99e263

Subscribe to this mod's changes

sprint-planner is a skill published in the GitHub repository vmobifystudio/app-dev-team (4 stars, last pushed 24d ago), licensed MIT. It adds 53 tokens to every session and 3,314 once invoked, about $0.0003 per session on Opus 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-03.

Autonomous Agents Planning Project management agent-orchestration ai-agents android claude-code claude-code-plugin

resume

Load context for a fresh session in a worktree with in-flight pair-flow work. Reads the kickoff brief (the contract), tasks.md state, recent git log, the open PR state, and an optional handover brief, then surfaces uncommitted changes and asks before proceeding. Read-only over your in-flight work: no stash, clean…

inkatze/planwright · 95 tokens

seeds-issue-audit

Audit and triage open Seeds (sd) issues — find which can be closed, auto-close high-confidence completed ones, and report borderline cases. Activate for prompts like "audit open issues", "which seeds issues can be closed", "clean up the issue tracker", "triage the seeds backlog".

jayminwest/warren · 67 tokens

good-first-issue-batch

File a batch of contributor-ready GitHub issues from the seeds backlog, re-verifying every candidate against HEAD first so no dead issue reaches a contributor. Activate for prompts like "file some good first issues", "open a batch of GFIs", "publish backlog issues to GitHub", "find contributor-ready work", or after an…

jayminwest/warren · 80 tokens

warren-dogfood-pipeline

Full prioritize → dispatch → shepherd → track pipeline against the live warren instance. Audits the seeds backlog around a focus theme, dispatches the surviving issues to warren agents one at a time, babysits the resulting PRs to merge (update-branch, conflict-repair runs, auto-merge), and closes the loop in the…

jayminwest/warren · 116 tokens

run

Conduct a task end to end, from a one-line fix to a multi-day programme - a short interview, then autonomous execution to the finish. Classifies the task S/M/L/XL, configures itself to the repo, routes each role to a cost tier, drives the agent team from the kanban board, and stops only at genuine decisions. Use for…

jjanczur/tyran · 97 tokens

status

Where is the work right now. Regenerates the projections and the kanban board from the journal and answers with the progress line, the agents still running, the open gates and the resume steps. Read-only. Use for /tyran:status or when asked what is going on.

jjanczur/tyran · 58 tokens