One-click install
npx skills add https://github.com/anukkrit149/anukkrit-skills --skill planning-anukkrit149
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning
Source: https://github.com/anukkrit149/anukkrit-skills/tree/main/cloud/skills/planning
Command: npx skills add https://github.com/anukkrit149/anukkrit-skills --skill planning-anukkrit149

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of turning an ambiguous coding task into a concrete, step-by-step execution plan that identifies what to change, what to test, and what risks to watch for.

Core Features & Use Cases

  • Task understanding and acceptance criteria mapping: Extracts outcomes, constraints, and requirements from the prompt or issue.
  • Codebase exploration and relevant-file selection: Locates the repository structure, tech stack, and the most relevant modules and entry points.
  • Actionable planning with explicit test and verification steps: Produces a structured todo list including test writing and test-running, plus a final review/validation step.
  • Risk assessment: Flags breaking-change risks, edge cases, and uncertain areas for review.

Quick Start

Use the planning skill to create an implementation plan for a feature request by asking it to “Plan how to implement this change in the repo, including which files to edit or create, what tests to add, how to run the test suite, and what risks to flag.”

Frequently Asked Questions about planning

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

FAQPage Schema
How do I create an implementation plan for a new feature in my codebase?

An implementation plan clarifies how to execute a coding task by inspecting your codebase to identify relevant files, generating a step-by-step todo list, and flagging potential risks. It turns ambiguous feature requests into concrete code changes and testing steps.

What should be included in an actionable implementation plan for a bug fix?

An actionable implementation plan for a bug fix should include identified files to modify, a step-by-step todo list generated via write_todos, explicit test writing and running steps, and a final validation review. It must also feature a risk assessment flagging breaking changes and edge cases.

Does automated planning work for refactoring tasks and PR preparation?

Automated planning works for refactoring tasks and PR preparation by inspecting the repository structure, selecting files to modify or create, and mapping out verification steps. It fits scenarios where you must clarify requirements and identify testing steps before submitting code changes.

How do I identify relevant files and entry points before coding a new feature?

You identify relevant files and entry points by performing codebase exploration to detect the tech stack and repository structure. This analysis locates the most relevant modules, allowing you to select exactly which files to modify or create before generating a step list.

What is the best way to assess breaking-change risks before modifying a repository?

The best way to assess breaking-change risks before modifying a repository is to perform a dedicated risk assessment during implementation planning. This flags uncertain areas, edge cases, and potential breaking changes for review before you execute any code changes.