From quangflow
Use when entering execution handoff — ROADMAP generation, TDD/logging mandates, SHIP/REFINE gate
npx claudepluginhub duongmquang/quangflowThis skill uses the workspace's default tool permissions.
You are now entering Phase 3: Execution Handoff.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
You are now entering Phase 3: Execution Handoff.
See _protocols/_shared.md → State Check Template. Required artifacts: REQUIREMENTS.md + DESIGN.md.
If missing DESIGN.md: "No design found. Run /qf:2-design first."
If missing REQUIREMENTS.md: "No requirements found. Run /qf:1-brainstorm <idea> first."
See _protocols/_shared.md → Milestone Detection. Target artifact: ROADMAP.md.
Read REQUIREMENTS.md (project-level) + DESIGN.md (milestone-level) + CONTEXT.md (if exists).
See _protocols/_shared.md → GOTCHAs System → Review Protocol.
Read both plans/GOTCHAS.md (global) and plans/{feature-slug}/GOTCHAS.md (feature) if they exist. Filter by tags matching this milestone's requirements.
If relevant gotchas found: inject their rules as > ⚠️ GOTCHA [global/feature]: warnings in the appropriate ROADMAP.md phases.
When generating ROADMAP.md, inject these requirements into EVERY implementation phase:
All implementation phases MUST follow TDD (see _tdd-enforcement.md). All application code MUST use structured logging (see _structured-logging.md). All phase transitions MUST have verification evidence (see _verification-gates.md).Each ROADMAP.md implementation phase must include:
Before generating artifacts, load the feature's FMU via @mention (see _context-memory.md).
If no FMU exists for this feature, create one in .memory/{feature-slug}/ with CONTEXT.md.
Generate to ./plans/{feature-slug}/:
REQUIREMENTS.md (project-level) — UPDATE the existing draft:
CONTEXT.md (project-level) — append locked decisions from this milestone
OPEN_QUESTIONS.md (project-level) — append/update open items
Generate to ./plans/{feature-slug}/milestone-{N}/:
See _protocols/_shared.md → Code Quality Mandates. Inject into every ROADMAP phase.
For each phase in the generated ROADMAP.md:
Split rules:
Skip condition: If ALL phases are already ≤150 LOC and ≤3 REQ-IDs, skip silently.
Autopilot mode: See _protocols/_autopilot.md → Phase 3 — Handoff.
Normal mode:
Agent waits. Does nothing until user types CONFIRM.
See _protocols/_shared.md → Output Rule.
After CONFIRM, check REQUIREMENTS.md for team_mode and team_composition settings.
If team_mode: true:
Read team_composition from REQUIREMENTS.md
Map ROADMAP.md phases to team roles based on file ownership boundaries
Present the execution plan:
"Team mode enabled. Here's the execution plan:
| Role | Type | Phases | File Ownership |
|---|---|---|---|
| lead | Orchestrator | Coordinate all | Main session |
| domain-engineer | Architect (recommended) | Before devs | plans/{slug}/milestone-{N}/design/ |
| dev-backend | Developer | Phase 1, 3 | src/api/*, src/models/* |
| dev-frontend | Developer | Phase 2, 4 | src/components/*, src/pages/* |
| tech-lead | Reviewer (optional) | After devs | Read-only on all dev files |
| tester | Tester | After review | tests/* |
Pipeline: domain-engineer designs -> devs implement (parallel) -> [optional] tech-lead reviews -> tester tests
Options:
/qf:cook)Autopilot shortcut: See _protocols/_autopilot.md → Phase 3. Auto-SHIP, skip REFINE.
On REFINE:
team_composition in REQUIREMENTS.md after each refinementOn SHIP:
/qf:cook — cook.md is the single source of truth for pipeline orchestrationteam_composition from REQUIREMENTS.md and executes the full pipelineIf team_mode: false (or not set):
team_mode: true automatically — multi-agent is the only modeSee _protocols/_shared.md → Progress Tracking. Append Phase 3 row to plans/{feature-slug}/PROGRESS.md.
Key decisions to log: execution mode (SHIP), ROADMAP phase count, team composition summary.
Tell user: "Phase 3 complete for milestone-{N}. Artifacts saved to ./plans/{feature-slug}/milestone-{N}/."
Then suggest next command based on mode:
If team_mode: true:
**Next:** `/qf:cook` — Launch team pipeline (domain-engineer -> devs -> tech-lead -> tester -> PM)
=> Skip? You can implement manually (Solo mode) — run `/qf:4-verify` after implementing
=> Also available: `/qf:status` (check status), `/qf:status save` (save context)
Solo mode has been removed. All execution runs through /qf:cook.