planning

Develop comprehensive implementation plans for non-trivial code changes.

1|Updated Mar 7, 2026

Search Tags:#pre-implementation #code planning #design decisions #test-first development #developer collaboration

Ready to run

npx skills add https://github.com/cosmoscalibur/agent-hardness --skill planning-cosmoscalibur

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: planning
Source: https://github.com/cosmoscalibur/agent-hardness/tree/main/skills/planning
Command: npx skills add https://github.com/cosmoscalibur/agent-hardness --skill planning-cosmoscalibur

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The planning Skill addresses the challenge of preparing detailed implementation plans before non-trivial code changes, ensuring alignment with team objectives and minimizing errors.

Core Features & Use Cases

Pre-Implementation Planning: Outlines scope, key design decisions, and open ambiguities before starting any non-trivial implementation.
Task Framing: Ensures tasks are verifiable and test-first, promoting a quality-first approach.
Developer Collaboration: Flags decisions requiring developer consultation and autonomous resolutions.

Quick Start

Run the planning skill to create a comprehensive plan for your upcoming feature.

Frequently Asked Questions about planning

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

FAQPage Schema

How do I create a pre-implementation plan for non-trivial code changes?▼

Pre-implementation planning for non-trivial code changes involves outlining scope, key design decisions, and open ambiguities before starting development to ensure alignment with team objectives and minimize errors. It creates a comprehensive roadmap for the upcoming feature.

What is test-first task framing in software development planning?▼

Test-first task framing is a planning technique that ensures development tasks are verifiable and promote a quality-first approach. It structures implementation requirements so that validation criteria are defined before any code is written.

When do I need to outline design decisions before starting code implementation?▼

You need to outline design decisions before code implementation whenever preparing non-trivial changes. Defining these decisions early resolves open ambiguities, establishes clear scope, and ensures the resulting code aligns with development objectives.

How do I flag design decisions for developer collaboration during planning?▼

Flagging design decisions for developer collaboration involves identifying which aspects of the pre-implementation plan require team consultation versus autonomous resolution. This ensures alignment on scope and minimizes implementation errors before coding begins.

Does planning work for complex feature scoping without external dependencies?▼

Yes, the planning process works independently without external dependencies to define scope and task framing. It autonomously resolves straightforward implementation details while explicitly flagging complex design decisions requiring developer consultation.