Skill Pantry · Gaiya365

Planning

Writing Plans

Convert a broad specification into explicit implementation tasks.

PlanningMITChecked Oct 18, 2026

Our review

This text-only skill treats a plan as an interface for the next implementer. It asks for concrete files, steps, tests, expected outputs, and a handoff that makes hidden assumptions visible. It covers scope checks and task sizing so an engineer or agent with limited context can pick up the work without reconstructing every earlier decision.

Use it when a feature spans several files or needs sequencing across work areas. Skip it for a tiny change whose exact edit and verification are already clear. The skill assumes a test-first and frequent-commit workflow; those defaults may need adapting to a repository’s own rules. A plan can become stale as implementation reveals facts, so update the affected steps rather than treating the document as infallible.

The folder contains only SKILL.md, with no bundled script or direct network behavior. It may suggest ordinary version-control and test commands for the user’s project. Read the plan it produces before handing it to another agent, especially where it proposes destructive or external actions.

For installation, open the linked maintainer folder and read its current SKILL.md, license, and supporting files. Copy the complete folder to a skills location your agent documents, or use an installer your agent supports. Begin with a small, low-risk task and confirm that the agent loaded the intended version. Our install guide covers those checks.

Source and license

Maintainer: Jesse Vincent / obra. Checked: October 18, 2026. The maintainer controls this repository; the current files may differ from the version we reviewed.

Repository ↗ · SKILL.md ↗ · MIT license ↗

← Browse all skills