project-init

Scaffold a .context/ workspace with agents, skills, and documentation.

1|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/NEXUZ-SYS/devflow --skill project-init-nexuz-sys
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-init
Source: https://github.com/NEXUZ-SYS/devflow/tree/main/skills/project-init
Command: npx skills add https://github.com/NEXUZ-SYS/devflow --skill project-init-nexuz-sys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

DevFlow project initialization is often lengthy and error-prone; this skill automates scaffolding the .context/ structure and project-aware agents, skills, and documentation to ensure a consistent baseline for new projects.

Core Features & Use Cases

  • Scaffolds .context/ with initial structure for agents, skills, docs, and plans.
  • Initializes language settings and propagates them to dotcontext MCP to enable full-content generation.
  • Handles zero-downtime initialization by detecting existing context and delegating to context-sync when appropriate.

Quick Start

Use the project-init skill to scaffold a fresh .context/ with project-aware agents, skills, and docs.

Frequently Asked Questions about project-init

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

FAQPage Schema
How do I scaffold a .context workspace for a new DevFlow project?

To scaffold a .context workspace, this skill automates the initial DevFlow project setup by generating a consistent, dotcontext-v2 compatible structure with project-aware agents, skills, and documentation.

What is the best way to initialize project context without causing downtime?

Zero-downtime initialization is achieved by detecting existing context within the workspace and delegating synchronization to context-sync, ensuring safe initialization without disrupting active workflows.

Does project initialization work in standalone mode or does it require MCP?

Project initialization supports both standalone and MCP-based modes, integrating with dotcontext MCP to enable full-content generation while maintaining a consistent .context structure.

Can I propagate language settings to dotcontext MCP during project setup?

Yes, during project setup, language settings are initialized and automatically propagated to dotcontext MCP to enable full-content generation tailored to your language preferences.

Why does DevFlow project setup require a .context directory structure?

A .context directory structure is required to provide a consistent baseline for new DevFlow projects, organizing initial structures for agents, skills, docs, and plans to prevent error-prone manual setup.