flow-planner
Plan phases, tasks, and iterations. Use when structuring new work, adding features, or organizing development plans.
Découvrez les skills DevOps, comparez leurs dépôts et consultez leurs instructions.
Plan phases, tasks, and iterations. Use when structuring new work, adding features, or organizing development plans.
Choose names that fully and accurately describe what the variable represents
Interactive idea refinement using Socratic method to develop fully-formed designs
Execute implementation work with gate checks and verification. Use when user wants to code, build features, implement iterations, or execute action items. Enforces gates, guides workflow, tracks progress.
Mark tasks and phases complete after verification. Use when finishing tasks, closing phases, or marking work done. Ensures all work verified before completion.
Execute implementation plan by dispatching fresh subagent for each task, with code review between tasks
Dispatch code-reviewer subagent to review implementation against plan or requirements before proceeding
Execute detailed plans in batches with review checkpoints
Create isolated git worktrees with smart directory selection and safety verification
Complete feature development with structured options for merge, PR, or cleanup
Refactor with tests first, one change at a time, never mix refactoring with bug fixes or new features
TDD for process documentation - test with subagents before writing, iterate until bulletproof
Never test mock behavior. Never add test-only methods to production classes. Understand dependencies before mocking.
Validate at every layer data passes through to make bugs impossible
Replace arbitrary timeouts with condition polling for reliable async tests
Write the test first, watch it fail, write minimal code to pass
Receive and act on code review feedback with technical rigor, not performative agreement or blind implementation
Check all external inputs for validity - garbage in, nothing out, never garbage out
Maintain skills wiki health - check links, naming, cross-references, and coverage
Write comments explaining WHAT and WHY, never temporal context or history
Lightweight, git-native issue tracking (aka beads) for AI agents. Use for creating, planning, updating, and tracking issues with dependencies. Invoke when user mentions tbd, beads, to-do lists, planning, tracki...
Use when building NuxtHub v0.10.4 applications - provides database (Drizzle ORM with sqlite/postgresql/mysql), KV storage, blob storage, and cache APIs. Covers configuration, schema definition, migrations, mult...
Clarify ambiguous requests by researching first, then asking only judgment calls; stop before implementation.
Create micro-commits (minimal incision) with at least one validation signal per commit.
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.