trycycle-planning

Implementation plans map scope, file changes, testing, and commits into bite-sized tasks saved as Markdown documents. They assume zero codebase context, detailing exact files to touch, tests to run, and documentation to check before starting.

To break down software engineering tasks, the Skill applies DRY, YAGNI, and TDD principles to produce bite-sized tasks, defining clear file structures, interfaces, and dependencies needed for each step before any code is written.

Yes, this implementation planning tool is specifically designed for unknown codebases by documenting every file change, interface, and testing requirement an engineer needs, assuming they have zero prior context about the project.

The best way to document file changes and testing for new features is using an end-to-end plan that maps tasks to code modifications and test strategies, automatically saved to a reusable docs/plans/YYYY-MM-DD-<feature-name>.md file.

Yes, you can use this for task decomposition and defining interfaces before coding. It automatically structures the implementation plan by mapping out file dependencies, interfaces, and task-level guidance prior to any actual development.