impl-doc

To generate an implementation guide for a development task, provide the design document for your CLI tool, backend endpoint, or frontend component to produce a structured, phase-based roadmap for coding.

Phase-based planning is breaking down small software tasks into logical, verifiable steps like INIT, CORE, IO, API, DB, UI, TEST, and PKG to ensure consistent implementation and prevent scope creep before coding begins.

You can plan task dependencies and verification scenarios for an API endpoint by generating a standardized implementation guide that includes dependency tracking, agent instructions, and verification criteria.

No, this implementation guide generation approach does not suit full-stack multi-screen planning; it is specifically designed for individual modules, CLI tools, backend endpoints, or frontend components.

You need structured documentation for small frontend components to prevent scope creep, map task dependencies, and ensure all edge cases are covered with verifiable steps before the actual coding begins.

Yes, you can use this for adding a single API endpoint to your backend, as it generates a step-by-step implementation guide tailored for small-scale features and individual modules.