flutter-development-guide

Guide Flutter development teams through a three-stage specification, planning, and implementation workflow.

6|3|Updated Aug 19, 2025
One-click install
npx skills add https://github.com/utakata-code/flutter_init --skill flutter-development-guide
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flutter-development-guide
Source: https://github.com/utakata-code/flutter_init/tree/main/.agent/skills/flutter-development-guide
Command: npx skills add https://github.com/utakata-code/flutter_init --skill flutter-development-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Flutter development teams often struggle to coordinate requirements, architecture planning, and staged implementation, leading to drift and delays. This Skill provides a clear, repeatable process that guides users through Stage 1 (specification), Stage 2 (structure planning), and Stage 3 (implementation) using a mode-based workflow and centralized guidelines.

Core Features & Use Cases

  • Structured, stage-based development lifecycle (Stage 1: specification, Stage 2: structure planning, Stage 3: implementation) to align teams.
  • Mode-based guidance: Mode 1 (new app), Mode 2 (existing app with rules), Mode 3 (existing app without rules) to tailor workflows.
  • Centralized references and templates to keep documentation in sync with code throughout the project lifecycle.

Quick Start

モードを選択して Stage1 から Stage3 のワークフローに従い、AI 指示群を利用して開発を進めてください。

Frequently Asked Questions about flutter-development-guide

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure a Flutter development workflow to prevent requirement drift?

A structured Flutter development workflow prevents drift by enforcing a three-stage lifecycle: specification, structure planning, and implementation. It aligns teams through mode-based guidance and centralized templates to keep code and documentation in sync.

What is the best way to manage Flutter app refactoring without existing architecture rules?

Managing Flutter app refactoring without existing rules uses Mode 3, which guides existing apps without declared rules. The workflow applies a three-stage lifecycle to establish specifications, plan structure, and implement changes systematically.

How do I plan a new Flutter app architecture from specification to implementation?

Planning a new Flutter app architecture follows Stage 1 specification, Stage 2 structure planning, and Stage 3 implementation. Mode 1 provides tailored guidance for new applications using centralized references and templates throughout the lifecycle.

Can I apply a staged development process to an existing Flutter app with established rules?

Yes, you can apply a staged development process to existing Flutter apps with established rules using Mode 2. This mode tailors the three-stage workflow to respect current rules while coordinating structure planning and implementation.

Why does my Flutter team struggle with delays during architecture planning and implementation?

Flutter teams experience delays during architecture planning and implementation due to uncoordinated requirements and lack of a repeatable process. A stage-based workflow with centralized guidelines and status-tracking artifacts enforces alignment and reduces drift.

When do I need centralized templates in a Flutter development lifecycle?

You need centralized templates in a Flutter development lifecycle to keep documentation in sync with code throughout the project. They provide repeatable structures for specification, structure planning, and implementation across all development modes.