v1.7.0

plan-agent v1.7 — self-describing HTML plans

Implementation plans now auto-build their own file-tree and expose copyable paths

Auto-generated file-tree: file paths extracted straight from the plan's steps, no hand-maintained list
Each path classified new / modified / deleted / generated by the step's action verb, then grouped by directory
Classification precedence when a file recurs: deleted > new > generated > modified
Copyable plan-source block: one-click copy of the plan's filename and relative path
plan-file and plan-path meta tags added; backfilled across all 24 existing plans — pure CSS, no CDN

A plan document that maintains its own file map — without anyone updating a list.

The latest plan-agent release (v1.7) changes how Claude Code writes implementation plans. Two upgrades stand out:

→ Auto-generated file-tree. Instead of asking the author to hand-maintain a list of touched files (which always drifts), the skill now derives it from the plan's steps — parsing every file path, inferring new / modified / deleted from the action verb, and grouping by directory. The file map can't go stale because it's computed, not typed.

→ Copyable plan source. Every plan now renders its own filename and relative path with one-click copy buttons, plus machine-readable meta tags — so you can drop a plan's location straight into docs or a follow-up prompt.

The constraint that keeps it durable: pure CSS and inline SVG, no CDN or charting library. Every plan stays a single self-contained HTML file you can open offline. All 24 existing plans were backfilled, so the whole gallery is consistent.

Run it: /plan-agent:implementation-plan <objective>

Follow for more Claude Code plugin breakdowns like this.

#ClaudeCode #DeveloperTools #AITools #Automation

Twitter/X

plan-agent v1.7: Claude Code implementation plans now build their own file-tree from their steps — paths parsed, new/modified/deleted inferred from the action verb, grouped by directory. No hand-maintained list to go stale. Pure CSS, self-contained HTML. #ClaudeCode #DeveloperTools

Bluesky

Nice update in Shawn Sandy's plan-agent (v1.7): Claude Code implementation plans now auto-build their own file-tree from the steps — paths parsed, new/modified/deleted inferred from the verb, grouped by directory. The file map is computed, so it can't drift. Pure CSS, self-contained HTML.

Substack

The most interesting thing about plan-agent's v1.7 release isn't a feature — it's a principle: derive, don't ask. Implementation plans used to carry a hand-maintained list of the files they touched, and like all duplicated state, it drifted. Now the skill computes the file-tree from the plan's own steps — parsing paths, inferring new/modified/deleted from each action verb, grouping by directory. Pair that with copyable plan paths and a 24-plan backfill, and you get plan documents that stay honest about themselves.

Follow for more on Claude Code plugin design.