A top-level workflow for implementing a Flutter feature from a product requirements document and a technical specification. It runs task planning, implementation, verification, and review in sequence.

Use it when the PRD and technical specification are complete and ready to turn into code. It coordinates tasks, runs the build and test checks, and reviews the resulting changes.

It connects the major development stages so the feature can move from approved specifications to an implemented, checked, uncommitted change without pauses for approval.

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

Your own site

<a href="https://agentmods.dev/skills/strvcom/flutter-template/start-job"><img src="https://agentmods.dev/badge/skills/strvcom/flutter-template/start-job/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/start-job"><img src="https://agentmods.dev/badge/skills/strvcom/flutter-template/start-job.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,138 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.00078	$0.01138
Opus 5.5	$0.00031	$0.00455
Sonnet 5.5	$0.00016	$0.00228
Haiku 4.5	$0.00008	$0.00114

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

Security

Grade A, and why

start-job 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/start-job/SKILL.md · 93 lines

How it starts

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

Flutter Template Start Job

Single entry point that runs the post-spec Flutter implementation pipeline. It is designed to be invoked once, with no user input between phases, so the feature goes from "spec approved" to "verified, uncommitted implementation" in one shot.

Use this only after the PRD and tech spec are finished. If another agent or developer is still editing the tech spec, do not start implementation yet.

Prerequisites

PRD exists at .claude/tasks/[feature-name]/prd.md
Tech Spec exists at .claude/tasks/[feature-name]/techspec.md
The tech spec is complete and no other agent is actively editing it.
The current working tree does not contain unresolved conflicts in .claude/tasks/[feature-name]/.

If the PRD or techspec is missing, stop and ask the user to run /prd and/or /techspec first. If the tech spec appears to be in progress, stop and ask the user to confirm it is ready.

Pipeline

Run each phase in order. Do NOT ask for user approval between phases. Do NOT commit anything at any point. If a phase fails hard (cannot proceed), stop and surface to the user.

Critical orchestration rule: when a sub-skill returns control, do not treat its output as the end of your turn. You are still inside this /start-job orchestrator. Immediately invoke the next phase's skill in the same response. Do not stop, do not summarize, do not pause for user input between phases. The only valid stops are: (a) hard failure, (b) the Final Report after Phase 4.

Phase 1 — Task Breakdown

Invoke the tasks skill. It generates tasks.md and individual task files under .claude/tasks/[feature-name]/. No approval prompt.

After tasks returns: do not stop, do not wait for input, do not summarize. Immediately invoke implement-tasks-sequence (Phase 2) in the same response.

Phase 2 — Implementation

Invoke the implement-tasks-sequence skill. It executes all generated tasks in dependency order, parallelizing when safe. No per-task builds, tests, or commits — agents only write code changes.

Read the full file on GitHub · 93 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 · 93 lines · 78 tokens per session scan A 91621ef7e7b5

Subscribe to this mod's changes

start-job is a skill published in the GitHub repository strvcom/flutter-template (24 stars, last pushed 4mo ago), licensed MIT. It adds 78 tokens to every session and 1,138 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-08-30.

Mobile Planning

start-job next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
start-jobstrvcom/flutter-template	Skill	24	4mo ago	MIT	A	78	Claude Code
orca-emulator-androidstablyai/orca	Skill	117k	yesterday	MIT	A	102	Claude Code, Codex
glance-canonical-layoutsandroid/skills	Skill	10k	yesterday	Apache-2.0	A	56	Claude Code
android-tombstone-symbolicationdotnet/skills	Skill	5.8k	yesterday	MIT	A	176	Claude Code
dogfoodcallstack/agent-device	Skill	5.3k	yesterday	MIT	A	55	Claude Code
winapp-mauimicrosoft/winappCli	Skill	1.4k	yesterday	MIT	A	68	Claude Code
app_remixrome-os/rome	Skill	889	yesterday	MIT	A	50	Claude Code, Codex

flutter-template: Skill for Claude Code