trycycle-planning

Generate implementation plans with file changes, tests, and documentation.

3|Updated Jan 14, 2014

Search Tags:#planning #testing #documentation #codebase #implementation #task-decomposition

Ready to run

npx skills add https://github.com/prateek/dotfiles --skill trycycle-planning-prateek

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: trycycle-planning
Source: https://github.com/prateek/dotfiles/tree/main/.agents/skills/trycycle/subskills/trycycle-planning
Command: npx skills add https://github.com/prateek/dotfiles --skill trycycle-planning-prateek

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Write comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste. Document everything they need to know: which files to touch for each task, code, testing, docs they might need to check, how to test it. Give them the whole plan as bite-sized tasks. DRY. YAGNI. TDD. Frequent commits.

Core Features & Use Cases

Map out which files to touch, modules to modify, tests to write, and documents to consult.
Enforce DRY, YAGNI, and TDD principles; present the plan as bite-sized tasks and clear checkpoints.
Save plans to the planned location and include plan headers, task structure, and acceptance criteria.

Quick Start

Draft a feature plan for a feature in an isolated workspace following the trycycle-planning guidelines.

Frequently Asked Questions about trycycle-planning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate an implementation plan for a feature with no existing codebase context?▼

To generate an implementation plan with zero codebase context, you need a tool that maps out which files to touch, modules to modify, and tests to write. This ensures engineers understand the entire task structure without prior knowledge.

What is the best way to break down a multi-subsystem software feature into bite-sized tasks?▼

The best way to break down multi-subsystem features into bite-sized tasks is by applying task decomposition principles like DRY, YAGNI, and TDD. This creates clear checkpoints and documents decisions for each specific file modification and test requirement.

How do I structure tests and documentation when planning a new software implementation?▼

To structure tests and documentation during implementation planning, define which test files to write and which documents to consult within the plan itself. This enforces TDD principles and ensures testing standards are met before coding begins.

Can I enforce DRY and YAGNI principles when creating a software development plan?▼

Yes, you can enforce DRY and YAGNI principles when creating a software development plan by structuring the plan to explicitly avoid repetition and unnecessary features. This produces a clear plan document with headers, task granularity, and acceptance criteria.

What should a comprehensive implementation plan document include for engineers with zero context?▼

A comprehensive implementation plan document should include a plan header, bite-sized tasks, which files to touch, testing strategies, and documentation standards. This provides the complete context needed for successful feature implementation.