existing-project-intake

What problem does it solve?

Starting development on an existing project with incomplete, stale, or missing documentation leads to building on incorrect assumptions, introducing regressions, and wasting effort on rework. This Skill eliminates that risk by enforcing a source-first intake process before any code changes are made.

Core Features & Use Cases

• Source-first project inventory: Derives the current true state of the project from code, tests, config, and git history instead of relying on potentially stale existing docs.
• Task-appropriate documentation baseline: Generates required core docs (project overview, PRD, QA tracker, etc.) or marks gaps as N/A with explicit reasons, avoiding unnecessary overhead for small targeted changes.
• Regression and QA readiness audit: Identifies missing, unsafe, or unguarded QA/regression endpoints to prevent accidental production exposure and ensure deterministic testing is possible.
• Use Case: For example, if you inherit a legacy internal tool with no up-to-date docs and missing test coverage, use this Skill to first inventory the source, create a minimal truthful docs baseline, and confirm safe QA hooks before implementing any new features.

Quick Start

Invoke the existing-project-intake skill to perform a full intake and generate a truthful documentation baseline for the existing project you need to continue developing.