Help us improve
Share bugs, ideas, or general feedback.
From quangflow
Initializes projects or features by scanning codebase at shallow/medium/deep depths, creating CONTEXT.md, detecting project type, and setting technical/autopilot modes.
npx claudepluginhub duongmquang/quangflow --plugin quangflowHow this skill is triggered — by the user, by Claude, or both
Slash command
/quangflow:0-initThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are now entering Phase 0: Project Init.
Guides users through structured codebase exploration and clarifying questions to refine a feature idea into a design spec.
Initializes projects: detects existing code, questions for requirements, researches via subagents, scopes needs, generates roadmap.
Guides technical evaluation of code review feedback: read fully, restate for understanding, verify against codebase, respond with reasoning or pushback before implementing.
Share bugs, ideas, or general feedback.
You are now entering Phase 0: Project Init.
Sets up project context before brainstorming. Run once per feature.
Separate project setup (who are you, what exists) from requirements discovery (what to build). Creates the scaffold and scans the codebase so all subsequent phases start with context.
/qf:0-init <idea> — Initialize with a feature idea
/qf:0-init — Initialize interactively (asks for idea)
./plans/{feature-slug}/Ask the user:
"Before we start — are you technical (developer/engineer) or non-technical (PM, founder, designer)?
pm_mode: hands-onpm_mode: autopilot — see _protocols/_autopilot.md for full behaviorSee _protocols/_autopilot.md → Hands-Free Mode. Offer restart with claude --continue --dangerously-skip-permissions.
Save state to PIPELINE-STATE.md (see _protocols/_shared.md → PIPELINE-STATE Schema).
Ask the user:
"Is this an existing project or a new project from scratch?
Ask scan depth:
"How deep should I scan the codebase?
./docs/. Recommended.Perform the scan based on user's choice:
./docs/ directory (if exists)src/ structure (2 levels deep)project_type: newSave to ./plans/{feature-slug}/CONTEXT.md:
# Context — {feature-slug}
## Metadata
```yaml
quangflow_version: "1.1.0"
pm_mode: {hands-on | autopilot}
project_type: {existing | new}
scan_depth: {shallow | medium | deep | none}
created: {ISO timestamp}
{detected stack from scan, or "TBD — will be decided in Phase 1/2"}
{directory tree summary from scan, or "New project — no existing structure"}
{patterns found during scan, or "N/A"}
{key deps relevant to the new feature, or "N/A"}
{any constraints from current architecture, or "None identified"}
(populated by later phases)
## Step 5: Create OPEN_QUESTIONS.md
Save to `./plans/{feature-slug}/OPEN_QUESTIONS.md`:
```markdown
# Open Questions — {feature-slug}
(populated during brainstorm and later phases)
Check ./plans/*/PIPELINE-STATE.md for hands_free: true.
If found: skip Autopilot Detection, resume from last incomplete stage.
If not found: proceed with Step 1 above.
See _protocols/_shared.md → Output Rule.
See _protocols/_shared.md → Progress Tracking. Append Phase 0 row to plans/{feature-slug}/PROGRESS.md.
Key decisions to log: project type (existing/new), scan depth, pm_mode.
Tell user: "Project initialized. Context saved to ./plans/{feature-slug}/CONTEXT.md."
Then suggest next command:
**Next:** `/qf:1-brainstorm` — Discover requirements, edge cases, milestones, and team composition
↳ Skip? Jump to `/qf:2-design` only if you already have REQUIREMENTS.md written manually
↳ Also available: `/qf:status` (check status)