makinari-fase-investigacion

Extract repository context by reading requirements, examining repo state, and identifying dependencies, constraints, and acceptance criteria. This investigation process captures code, documentation, and client constraints to produce a validated foundation for accurate planning.

The investigation phase is a pre-coding data collection step that gathers repository context, brand guidelines, and constraints. It validates requirements and produces a structured report, ensuring planners have a complete foundation before execution begins.

Identify project risks during context gathering by examining the repository state and highlighting missing sections or uncertainties. This risk awareness prevents blind execution by surfacing constraints and gaps that affect downstream planning.

Yes, you can summarize repo state and brand guidelines in a concise INVESTIGATION section. This structured reporting format captures dependencies, contracts, and acceptance criteria into a reusable reference that planners quote directly in the instance plan.

Yes, the investigation phase explicitly applies to projects with code, documentation, and client constraints. It captures these constraints alongside dependencies and acceptance criteria to fulfill data collection and validation needs before planning.

Perform an investigation phase when a project involves existing code, documentation, and client constraints that require validation. It is needed before planning to ensure all dependencies, contracts, and acceptance criteria are captured and structured.