df:new-project

Initialize a new DevFlow project with planning artifacts under .planning.

Updated Feb 6, 2026
One-click install
npx skills add https://github.com/AO-Cyber-Systems/devflow-claude --skill df-new-project
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: df:new-project
Source: https://github.com/AO-Cyber-Systems/devflow-claude/tree/main/skills/df-new-project
Command: npx skills add https://github.com/AO-Cyber-Systems/devflow-claude --skill df-new-project

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Initialize a new project with deep context gathering and planning artifacts to streamline project setup in DevFlow.

Core Features & Use Cases

  • Guided questions to establish goals, scope, and constraints for a new project.
  • Automatic creation of planning artifacts under the .planning directory, including PROJECT.md, ROADMAP.md, REQUIREMENTS.md, and STATE.md.
  • End-to-end startup workflow with gated steps to ensure validation and approvals before proceeding.

Quick Start

Run the df:new-project workflow to bootstrap a new DevFlow project.

Frequently Asked Questions about df:new-project

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

FAQPage Schema
How do I start a new project with automated roadmap and requirements generation?

To start a new project, this workflow automates initialization by guiding context-gathering questions and generating planning artifacts like ROADMAP.md and REQUIREMENTS.md under a .planning directory. It establishes a repeatable startup process with gated validation steps.

What is project initialization with deep context engineering?

Project initialization with deep context engineering is a process that uses guided questioning and optional research to gather project scope and constraints, then generates structured planning materials to maintain project memory and ensure a repeatable startup workflow.

Can I use this project initialization workflow without any external dependencies?

Yes, you can use this project initialization workflow without external dependencies. It operates independently with frontmatter-driven configuration to generate planning artifacts and manage end-to-end workflow gates, requiring no prerequisite components.

What is the best way to maintain project state and memory during setup?

The best way to maintain project state and memory during setup is by automatically generating a STATE.md file within a dedicated .planning directory, which preserves context and tracks workflow progress alongside other planning artifacts.

How does the workflow handle validation and approvals before committing project plans?

The workflow handles validation and approvals by preserving end-to-end workflow gates throughout the startup process, ensuring that all planning artifacts and project contexts are validated and approved before proceeding to subsequent steps.

When do I need a dedicated .planning directory for project artifacts?

You need a dedicated .planning directory for project artifacts when initializing a new project that requires structured planning materials like PROJECT.md, ROADMAP.md, and STATE.md to establish clear goals, scope, and a repeatable startup workflow.