coding-agent

A phased workflow for multi-file coding projects structures changes across five phases: clarify, reconnaissance, plan, implement, and verify. It coordinates architectural decisions and library integrations to maintain consistency across modules with auditable steps.

To manage architectural decisions across multiple modules, you follow a structured workflow that maps the repository structure, plans changes systematically, and enforces consistent practices. This ensures traceable and reproducible modifications across files.

You need a structured workflow for coding projects when creating or modifying features that span multiple files, integrating libraries, or making architectural decisions. It enforces a phased approach to keep repository changes auditable and consistent.

You discover repository structure by mapping the project with glob patterns to identify entrypoints, configs, and dependencies. This reconnaissance phase informs the implementation plan and ensures consistent guidance across affected modules.

No, this coding workflow operates without external dependencies or components. It relies on repository structure discovery and a phased approach to guide multi-file changes, making it applicable across different project environments.

The best way to coordinate feature implementation across files is using a repeatable workflow that progresses through clarification, reconnaissance, planning, implementation, and verification. This keeps architectural changes traceable and reproducible across modules.