A technical-specification workflow for turning a product requirements document into an implementation-ready plan for a Flutter app. It examines the project and describes how data, state, screens, and integrations should be built.

Use it after writing a PRD to create a technical specification covering reusable project patterns, implementation order, state management, navigation, networking, and backend integration.

It reduces uncertainty before coding by grounding technical decisions in the existing code patterns, architecture, and settled product requirements.

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

Your own site

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

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

When invoked 1,473 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.00064	$0.01473
Opus 5.5	$0.00026	$0.00589
Sonnet 5.5	$0.00013	$0.00295
Haiku 4.5	$0.00006	$0.00147

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

Security

Grade A, and why

techspec 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/techspec/SKILL.md · 139 lines

How it starts

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

Technical Specification

You are a technical specification expert translating PRDs into implementation-ready specs for this Flutter app. The stack is flutter_riverpod + riverpod_annotation for state, freezed

json_serializable for data classes, auto_route for navigation, dio for HTTP, Firebase services for backend, and FVM-pinned Flutter SDK.

Objectives

Translate the PRD into concrete technical guidance grounded in this codebase
Reuse existing patterns from lib/features/<feature>/ and primitives from lib/common/ before proposing new ones
Specify the data → state → UI → integration build order so the tasks skill can break it into ordered work units

Prerequisites

Required: .claude/tasks/[feature-name]/prd.md
Output: .claude/tasks/[feature-name]/techspec.md

Workflow

Step 0: Load Shared Context

Before reading the PRD, check whether .claude/tasks/[feature-name]/context.md exists. If it does, read it. Use its contents to skip re-deriving already-captured decisions (problem statement, target platforms, key product decisions, out-of-scope items) — do not ask the user about things already settled there.

Step 1: Analyze PRD

Read the PRD at .claude/tasks/[feature-name]/prd.md and extract:

Core requirements and constraints
Domain entities involved (data shapes, sources, lifetimes)
Platform scope — which of Android / iOS / web / desktop are in scope, and whether any platform-specific behaviors apply
Whether the feature touches Firebase services, native channels, or other integrations

Step 2: Deep Project Analysis

Explore the codebase to ground the spec in reality:

Look for existing features under lib/features/ that follow a similar shape and should be mirrored (the canonical pattern is *_page.dart + *_page_content.dart + *_state.dart + *_event.dart).
Check lib/common/ for reusable widgets, extensions, theming, formatters before introducing new primitives.
Inspect existing DTOs (lib/common/data/dto/), entities (lib/common/data/entity/), use cases, and providers for naming / mapping conventions. Add a repository layer only if the project already has one for this area or the spec explicitly justifies it.
Check lib/app/setup/setup_app.dart to see which services / integrations are actually active versus scaffolded.
Read AGENTS.md, docs/PROJECT_OVERVIEW.md, and docs/PROJECT_GUIDELINES.md for the canonical conventions.

Read the full file on GitHub · 139 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 · 139 lines · 64 tokens per session scan A 1e38ee140f62

Subscribe to this mod's changes

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

techspec next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
techspecstrvcom/flutter-template	Skill	24	4mo ago	MIT	A	64	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