38
GitHub Stars
6
Bundled Files
3 weeks ago
Catalog Refreshed
2 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstart where the catalogue uses aiagentskills.
npx veilstart add skill khgs2411/flow --skill flow-initializer- DASHBOARD_TEMPLATE.md5.0 KB
- MIGRATION_PATTERNS.md11.7 KB
- OTHER_TEMPLATES.md5.5 KB
- PLAN_TEMPLATE.md5.3 KB
- SKILL.md9.1 KB
- TASK_TEMPLATES.md6.1 KB
Overview
This skill initializes Flow projects from scratch, migrates existing documentation into Flow format, or modernizes older Flow structures to current patterns. It creates the multi-file Flow architecture (DASHBOARD.md, PLAN.md, phase/task files), performs backups before changes, and reports a clear summary of results. Use natural prompts like “start flow”, “migrate to flow”, or “update my plan”.
How this skill works
The skill detects which path to take: Blueprint (new project), Migrate (convert existing docs), or Update (modernize an old Flow). It validates input, searches the project root for source files when migrating, creates timestamped backups, and then writes or updates .flow/ files using templates. After actions it verifies required files and returns a concise summary and next steps.
When to use it
- You want to create a new Flow project from scratch ("start flow", "initialize").
- You have docs like PRD.md, TODO.md, PLAN.md and want them converted to Flow format.
- You have an old .flow/ structure that needs to be updated to current patterns.
- You need a dry-run preview before creating a specific project structure.
- You want automatic backups created before migrating or updating files.
Best practices
- Confirm whether you want AI-suggested structure or to provide an explicit numbered phase/task layout.
- Allow the skill to create backups; never skip backup for migrating or updating existing files.
- Review dry-run previews before approval when providing explicit structure lists.
- Keep prompts clear about scope (project purpose, main phases, V1/V2 priorities) for better suggested structures.
- Verify .flow/ does not exist or explicitly confirm overwrite to avoid data loss.
Example use cases
- Blueprint: "Set up Flow for my WebSocket chat app" — get suggested phases, approve, create DASHBOARD.md, PLAN.md, and phase/task files.
- Migrate: "Migrate TODO.md to Flow" — skill backs up TODO.md, groups items into phases, converts items to task files and writes DASHBOARD.md.
- Update: "Update my plan structure" — skill backs up .flow/, modernizes DASHBOARD.md and PLAN.md, converts standalone tasks to iteration format.
- Create from explicit structure: provide numbered phases/tasks; skill shows dry-run preview and creates .flow/ on approval.
- Recoverable migration: skill creates timestamped backups like TODO.md.pre-flow-backup-YYYY-MM-DD-HHMMSS before any changes.
FAQ
A timestamped backup is created before any changes (e.g., original.pre-flow-backup-YYYY-MM-DD-HHMMSS). The original content is preserved so migration is reversible.
How does the skill decide between suggested or explicit structure?
If your input includes numbered phases/tasks or explicit markers ("Phase 1:", "Task 2:"), it treats it as explicit and shows a dry-run. Otherwise it asks clarifying questions and suggests a structure.