flux-code-agent-check

To audit code implementation progress, provide the path to your implementation plan file to compare the current codebase against the defined plan. This detects missing, extra, or deviated features by checking the file system state.

An implementation audit verifies whether agents correctly implemented planned modules or diverged due to scope creep. It compares the codebase against the original technical plan to ensure development aligns with project goals and architectural requirements.

Yes, you need access to the SQLite-based Claim Chain database (cc.db) to update pipeline management status. The audit requires this database, along with pipeline state files and project root access, to synchronize development progress.

Yes, you can detect scope creep automatically by comparing file system state against a predefined technical plan. This synchronization identifies execution deviations and updates pipeline state files to reflect actual development session progress.

The best way to synchronize a project knowledge graph is to run an audit comparing the file system state against the implementation plan. This updates the internal cc.db database and pipeline state files to accurately reflect current development progress.

Run a code review for execution deviations during complex multi-agent coding tasks when you need to verify if agents have implemented planned modules. This allows timely course correction before scope creep significantly impacts the project.