project-initialization-phase

Generate eight project documentation files from questionnaire responses and codebase scans.

Updated Jan 5, 2026
One-click install
npx skills add https://github.com/Sjdjdiejdrirhdkjej/Claude-code-conductor --skill project-initialization-phase-sjdjdiejdrirhdkjej
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-initialization-phase
Source: https://github.com/Sjdjdiejdrirhdkjej/Claude-code-conductor/tree/main/.claude/skills/project-initialization-phase
Command: npx skills add https://github.com/Sjdjdiejdrirhdkjej/Claude-code-conductor --skill project-initialization-phase-sjdjdiejdrirhdkjej

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the full project initialization flow by guiding a structured questionnaire, scanning an existing codebase when present, and orchestrating the generation of eight foundational documentation files.

Core Features & Use Cases

  • Questionnaire-driven setup: Collects essential project context via a 15-question flow to populate templates.
  • Brownfield detection & scan: Detects tech stack and ERD from migrations to auto-fill architecture docs.
  • Documentation generation: Coordinates creation of eight docs (overview, system-architecture, tech-stack, data-architecture, api-strategy, capacity-planning, deployment-strategy, development-workflow) and an ADR baseline.
  • Use Case: Use /init-project in greenfield projects to bootstrap docs or apply to brownfield to surface architecture docs from code.

Quick Start

Run the /init-project command to start the guided setup and automatically produce the 8 docs in docs/project/.

Frequently Asked Questions about project-initialization-phase

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

FAQPage Schema
How do I automate project initialization and generate foundational documentation from scratch?

Automate project initialization by running a guided 15-question questionnaire that collects context and populates templates to generate eight foundational documentation files in your docs/project/ directory.

Can I generate architecture documentation for an existing brownfield codebase?

Generate architecture documentation for an existing brownfield codebase by scanning migrations to detect the tech stack and ERD, which automatically fills the architecture docs without manual input.

What foundational documents are created during the project setup workflow?

The project setup workflow creates overview, system-architecture, tech-stack, data-architecture, api-strategy, capacity-planning, deployment-strategy, and development-workflow docs, plus an ADR baseline.

How does the initialization process handle missing project context or unclear requirements?

The initialization process handles unclear requirements by validating cross-document consistency and explicitly marking unknown information with [NEEDS CLARIFICATION] tags for human review.

What's the best way to bootstrap docs for a greenfield project before writing code?

Bootstrap greenfield project docs by triggering the /init-project command to start the structured questionnaire flow and automatically orchestrate the creation of all eight foundational files.

Does the documentation generation require any external dependencies to run?

The documentation generation requires no external dependencies, operating entirely as a self-contained workflow to coordinate template filling, codebase scanning, and cross-document validation.