0-init

Automate project setup by generating CONTEXT.md and OPEN_QUESTIONS.md.

6|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/DuongMQuang/quangflow --skill 0-init
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 0-init
Source: https://github.com/DuongMQuang/quangflow/tree/main/plugins/quangflow/skills/0-init
Command: npx skills add https://github.com/DuongMQuang/quangflow --skill 0-init

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the initial project setup for a new feature by deriving a feature slug, selecting a PM mode, and generating CONTEXT.md and OPEN_QUESTIONS.md. It helps teams move quickly from idea to structured context before requirements discovery.

Core Features & Use Cases

  • Feature slug derivation from an idea or name and creation of a plan directory structure.
  • PM mode selection: hands-on for technical teams or autopilot for non-technical stakeholders.
  • Context generation: write CONTEXT.md with metadata about the feature, project type, and scan depth.
  • Open questions: create OPEN_QUESTIONS.md to capture uncertainties.
  • Pipeline-state logging: update PIPELINE-STATE.md to resume workflows after restarts.
  • Next-step guidance: provide recommended next steps and status checks.

Quick Start

Run /qf:0-init <idea> to initialize a new feature, derive its feature slug, and generate CONTEXT.md.

Frequently Asked Questions about 0-init

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the best way to generate project context and plan before discovering requirements?

Project context generation is best handled by deriving a feature slug, selecting a PM mode, and creating upfront context files to guide structured planning. This approach scans the codebase and captures metadata before requirements discovery.

How do I automate initial project setup for a new feature?

Automate initial project setup by running an initialization command with your idea to derive a feature slug, create a plan directory, and generate tracking files. This stepwise workflow moves your idea directly into structured context.

When do I need context generation and open questions files for project planning?

Context generation and open questions files are needed when starting a new feature to capture project metadata, scan depth, and uncertainties. These structured context artifacts ensure upfront planning and pipeline state tracking before development.

Can I use this planning workflow for existing projects or is it only for new ones?

This planning workflow applies to both new and existing projects, guiding feature scoping and codebase scanning. It adapts to your current environment by generating context and capturing open questions regardless of project age.

How does the pipeline state logging mechanism work for resuming workflows?

Pipeline state logging works by updating a dedicated state file to track workflow progress across phases. This mechanism ensures you can resume workflows seamlessly after restarts by logging the current stepwise status.

Does the PM mode selection support non-technical stakeholders?

PM mode selection explicitly supports non-technical stakeholders through an autopilot mode, alongside a hands-on mode for technical teams. This flexibility ensures appropriate guidance for feature scoping and upfront context creation.