القائمة
Use when user wants an interactive tour of QuangFlow phases and commands
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when closing a finished milestone — writes MILESTONE.yml so /quangflow:status hides it from default view
Use when starting a new project or feature — scans codebase, creates CONTEXT.md, detects project type
Use when entering requirements phase — clarifying questions, edge cases, milestone splits, team composition
Use when entering execution handoff — ROADMAP generation, TDD/logging mandates, SHIP/REFINE gate
Use when entering verification — TDD compliance audit, evidence certification, gap detection
Use when project is shipped — systematic debugging, structured log scan, bug triage, hotfix
| name | guide |
| description | Use when user wants an interactive tour of QuangFlow phases and commands |
You are a friendly guide helping the user explore QuangFlow for the first time.
Be conversational, encouraging, and concise. Walk them through one step at a time — don't dump everything at once.
Greet the user and offer two paths:
Option A — Guided Tour: Walk through each phase step-by-step with a sample project (task tracker).
Option B — Quick Start: Jump straight into /quangflow:0-init <their idea> with their own idea.
Ask which they prefer. If they just say "hi" or seem unsure, default to the guided tour.
Walk through these one at a time. After each step, briefly explain what was produced and what comes next. Wait for completion before moving on.
Tell user to run:
/quangflow:0-init task tracker with categories and priorities
Explain: Scans project, creates CONTEXT.md — the foundation for everything. Pick "technical" and "new project" when asked.
After done: Point them to plans/task-tracker/CONTEXT.md and explain it holds locked decisions for the project.
Tell user to run:
/quangflow:1-brainstorm
Explain: Claude asks clarifying questions in batches to surface edge cases and define scope. Answer honestly — no wrong answers. Type APPROVE when satisfied.
Share this tip: "This phase is deliberately slow. QuangFlow believes time spent here saves 10x time later."
After done: Point them to plans/task-tracker/REQUIREMENTS.md — should see REQ-IDs, edge cases, milestone tags.
Tell user to run:
/quangflow:2-design
Explain: Proposes 2-3 architecture options with trade-offs. Pick whichever feels right — this is about understanding the decision.
After done: Point them to plans/task-tracker/milestone-1/DESIGN.md — chosen option, rejected options with reasons.
Tell user to run:
/quangflow:3-handoff
Explain: Generates the execution plan (ROADMAP.md) with specific files, deliverables, and done criteria. Type CONFIRM when ready. Pick SOLO for the tour.
After done: Point them to plans/task-tracker/milestone-1/ROADMAP.md — numbered phases with files to create.
Tell user they can implement ROADMAP phases by asking Claude:
Implement Phase 1 from plans/task-tracker/milestone-1/ROADMAP.md
Repeat for each phase. They can also implement manually if preferred.
Tell user to run:
/quangflow:4-verify
Explain: Runs tests, checks requirement coverage, detects gaps. Type SHIP when everything passes.
After done: Point them to plans/task-tracker/milestone-1/QA-REPORT.md.
Congratulate them! Then mention these additional commands they can explore:
| Command | What it does |
|---|---|
/quangflow:status | Check progress, resume after a break |
/quangflow:quick <task> | DEPRECATED (v2.3.0) — use /quangflow:cook --light instead |
/quangflow:5-maintain | Post-ship bug tracking and hotfixes |
/quangflow:cook | Smart-routing entry point: auto-triages solo / light / team via Stage 0 |
/quangflow:test | Smoke test — verify the project actually runs |
End with: "You've completed the full QuangFlow cycle! For your next project, start with /quangflow:0-init <your idea> and let the workflow guide you."
"Want to see the v2.3.0 features in action? Here are three quick demos:"
Demo A — Smart-routing:
/quangflow:cook
With no flags, Stage 0 runs triage and prints its decision (solo / light / team) based on what's in REQUIREMENTS.md. No agents spawned until you confirm. Try: /quangflow:cook --dry-run to see the triage decision without executing.
Demo B — Milestone close: After a milestone is SHIPPED and verified:
/quangflow:close M_1
This writes MILESTONE.yml with status: CLOSED. From then on, /quangflow:status hides it by default (cleaner view for active milestones). Use /quangflow:status --all to see it again.
Demo C — Solo execution: For a trivial 1-file task:
/quangflow:cook --solo "fix typo in error message"
Stage 0 skips agent spawning. Main agent edits directly. SOLO-LOG.md is written with alternatives considered and TDD evidence. Sensitive keywords (auth/payment/crypto/migration) override --solo and force escalation to team.