A task-planning command that turns a product requirements document and technical specification into separate implementation tasks in dependency order. A product requirements document describes what should be built; a technical specification describes how.

Use it when the required PRD and tech spec already exist and you need task files that another agent can implement without further clarification.

It breaks a large feature into clear pieces that can be completed independently. Dependencies are made explicit so work can happen in a sensible order.

How strvcom/flutter-template configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to strvcom/flutter-template. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/strvcom/flutter-template/master/.agents/skills/tasks/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/strvcom/flutter-template

Made for: Claude Code.

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/strvcom/flutter-template/tasks/github.svg)](https://agentmods.dev/skills/strvcom/flutter-template/tasks)

Your own site

<a href="https://agentmods.dev/skills/strvcom/flutter-template/tasks"><img src="https://agentmods.dev/badge/skills/strvcom/flutter-template/tasks/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/strvcom/flutter-template/tasks"><img src="https://agentmods.dev/badge/skills/strvcom/flutter-template/tasks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

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

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original 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.1	$0.00113	$0.01557
Opus 5.5	$0.00045	$0.00623
Sonnet 5.5	$0.00023	$0.00311
Haiku 4.5	$0.00011	$0.00156

Measured 2mo ago against content hash d4c2f544623a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

tasks 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 2mo 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.

.agents/skills/tasks/SKILL.md · 150 lines

How it starts

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

Task Breakdown

You are specialized in breaking down features into discrete, manageable implementation tasks.

Objectives

Break down the feature into independently completable tasks
Establish clear dependency ordering
Create task files that an agent can execute without ambiguity

Prerequisites

PRD: .claude/tasks/[feature-name]/prd.md
Tech Spec: .claude/tasks/[feature-name]/techspec.md

Workflow

CRITICAL: Do NOT ask for approval.

The user does not want to review the task list before implementation. Generate the tasks, keep the total count reasonable (aim for cohesive tasks, not micro-tasks), and stop after reporting. The caller (/start-job or the user directly) decides what runs next.

Step 0: Load Shared Context

Before reading the PRD and tech spec, check whether .claude/tasks/[feature-name]/context.md exists. If it does, read it. Use its contents to skip re-deriving already-captured decisions — the problem statement, target platforms, architectural choices, and files to create are already settled. Do not re-ask the user about items already recorded there.

Step 1: Analyze PRD and Tech Spec

Read both documents and identify:

All components that need to be built
The dependency graph between components
Which tasks can be parallelized

Step 2: Generate Task Structure

Order tasks following this Flutter-stack progression (mirrors the .agents/templates/task-list.md phases):

Foundation (data layer) — DTOs in lib/common/data/dto/ (@freezed with generated fromJson factories), domain entities in lib/common/data/entity/, and Riverpod use cases/providers. Run make gen after annotation changes.
Core implementation (state + UI) — @riverpod notifiers, *_state.dart / *_event.dart (feature-scoped freezed types), and the page split: *_page.dart (thin @RoutePage widget) + *_page_content.dart (heavier UI).
Integration (navigation, services, platform) — @RoutePage wiring in lib/app/, Firebase / platform integrations, analytics events, permissions, native channels.
Tests and verification — only when explicitly required by the PRD / techspec. Standard analyze / test / build verification is handled by build-verify at the end of the flow, so don't add a "run analyze" task unless the feature itself requires custom coverage.

Read the full file on GitHub · 150 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.

2mo ago First seen · 150 lines · 113 tokens per session scan A d4c2f544623a

Subscribe to this mod's changes

tasks is a skill published in the GitHub repository strvcom/flutter-template (24 stars, last pushed 4mo ago), licensed MIT. It adds 113 tokens to every session and 1,557 once invoked, about $0.0005 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-08-30.

Planning Project management

tasks next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
tasksstrvcom/flutter-template	Skill	24	4mo ago	MIT	A	113	Claude Code
imagegenopenai/codex	Skill	133k	yesterday	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	99k	yesterday	Apache-2.0	A	19	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	4d ago	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	313k	3d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	95	Claude Code
next-partial-prefetching-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	103	Claude Code

flutter-template: Skill for Claude Code