skills.rest
Sixdd6
Sixdd6COMMUNITY
Explore all skills by this author →
GitHub

planning

Defines standards for writing implementation plans for features, fixes, and refactors.

Updated Sep 8, 2026
Search Tags:#planning#software engineering#code review#refactoring#verification#implementation plan
One-click install
npx skills add https://github.com/Sixdd6/grid-craft-launcher --skill planning-sixdd6
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: planning
Source: https://github.com/Sixdd6/grid-craft-launcher/tree/main/.claude/skills/planning
Command: npx skills add https://github.com/Sixdd6/grid-craft-launcher --skill planning-sixdd6

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It standardizes how implementation plans are created, reviewed, and executed in the GRID Craft Launcher repository, ensuring multi-file changes follow a consistent, verifiable structure. ## Core Features & Use Cases - Plan Trigger Rules: Defines when planning is required (multi-file changes, new modules, launch or download behavior changes) and when to skip it (one-file fixes, test-only changes). - Structured Plan Format: Enforces sections for Summary, Files table, numbered Steps with named agents, Verification, and Risks. - Required Reading: Directs planners to ARCHITECTURE.md, docs/SPEC.md requirement ids, domain skills, and docs/research/ before planning. - Use Case: When adding a new download feature, produce a plan whose steps each name an agent, the files it may touch, the test it runs, and the command proving completion. ## Quick Start Ask the assistant to create an implementation plan for a new launcher feature following the planning skill standards.

Frequently Asked Questions about planning

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

FAQPage Schema
When should I write an implementation plan before coding?▼

Write a plan when more than one file changes, the owning module is unclear, a new module or trait is added, or launch or download behavior changes. Skip planning for one-file bug fixes, test-only changes, and copy edits.

What sections should a software implementation plan include?▼

Include a two-to-four sentence Summary, a Files table with change reasons, numbered Steps naming the agent and test per step, a Verification section naming the verifier, and a Risks section describing what could break.

How do I make plan steps verifiable?▼

Each step must name the agent, the files it may touch, the test it adds or runs, and the command that proves it done. Steps must never say "handle errors" or "add tests" without specifying which.

What documents should I read before planning a feature?▼

Read ARCHITECTURE.md for the owning module, docs/SPEC.md for feature work while citing requirement ids, the relevant domain skill, and docs/research/ when the skill marks something VERIFY.

Can plan steps run in parallel?▼

Steps that touch the same file must be sequential. Only steps touching disjoint files can be parallelized safely.

Related Skills

Explore More Software Engineering Skills→
marcocellomarcocello
10

coding-research

Gather authoritative external evidence to resolve product, domain, library, or API uncertainties.

Community
Intermediate
Chulf58Chulf58

forge:implement

Automate the FORGE implement pipeline from approved plans to tested implementations.

Community
Advanced
SirTheOracleSirTheOracle

proposal-reviewer

Audit final plans against the codebase for correctness and regressions.

Official
Advanced
coco-researchcoco-research
264

gsd-fast

Execute trivial code changes directly in the current context.

Community
Basic