project-onboard

Automating project onboarding captures developer preferences and project constraints into persistent USER.md and PROJECT.md files. A six-phase structured interview gathers developer identity, working style, and access policies to ensure future sessions start with full context.

Persistent project context stores evolving project details and developer working styles in markdown files at the project root. It supports re-activation with updated context and partial-phase handling to avoid redundant questions during subsequent onboarding sessions.

Generating USER.md and PROJECT.md files requires completing a six-phase onboarding interview. This process captures developer identity, project constraints, access policies, and calibration, writing the output directly to the project root for persistent context.

Updating existing project context supports partial-phase handling to skip redundant questions. The onboarding interview can be re-activated to capture updated context for evolving projects without repeating previously completed phases.

Project onboarding requires no external dependencies or components to function. The six-phase interview operates independently to capture project context and generate persistent markdown files at the project root.

Structured interviews for project context capture are unnecessary for static, single-developer projects with no evolving constraints. If your project parameters never change and persistent context already exists, re-running the onboarding interview provides limited value.