TWISTEdBRACKETS

Skill

Planning

Turn specs into executable TDD task lists: greenfield (full scope) or delta (changed REQs only).

// workflow;

Behaviour

What it does

  • Reads docs/technical/ and, in delta mode, an approved impact report
  • Greenfield mode: plans all requirements; delta mode: only ADD/MODIFY/REMOVE items
  • Maps files to create and modify with explicit frozen scope on brownfield work
  • Breaks work into small TDD tasks with complete test code and verification steps
  • Self-reviews for gaps, placeholders, and scope creep
  • Saves the plan to docs/plans/
  • Hands off to project-setup (greenfield) or executing-plans (brownfield)

When to use

Good fits

After technical documentation on a greenfield project

After you approve an impact report on brownfield work

When you need a task breakdown an agent can execute without guessing

Development harness

Step 5 of 8 · Plan

Part of the design-to-ship pipeline: brainstorming → technical-documentation → conformance-check → reconciling-changes → planning → project-setup → executing-plans → shipping. Install the full set for structured feature work.

Install

Get this skill

Uses Agent Kit via npx; no global install required.

Quick install

sh
npx @levi-putna/agent-kit@latest add levi-putna/skills --skill planning

Global (Cursor)

sh
npx @levi-putna/agent-kit@latest add levi-putna/skills --skill planning --global --agent cursor

Global (Claude)

sh
npx @levi-putna/agent-kit@latest add levi-putna/skills --skill planning --global --agent claude

Project install

sh
npx @levi-putna/agent-kit@latest add levi-putna/skills --skill planning --project

Interactive install

sh
npx @levi-putna/agent-kit@latest add levi-putna/skills

Uninstall

sh
npx @levi-putna/agent-kit@latest remove planning

Example

Example prompt

Planning

Write a delta plan from the impact report. Only touch what is listed.

Flow

How the skill works

  1. Read the technical docs and any approved impact report
  2. Choose greenfield or delta mode and honour frozen scope
  3. Map affected files and break work into TDD tasks
  4. Self-review for gaps and ambiguities
  5. Save to docs/plans/ and hand off to the build phase