Tpp

Skill photostructure/coding-skills/plugins/coding/skills/tpp

Opinionated Claude Code and Codex workflow skills: iterative planning, proof-based review, and clean Conventional Commits.

Install

npx -y skills add photostructure/coding-skills --skill tpp

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Work on a Technical Project Plan — read the plan, identify the current phase, do that phase's work, and update the plan with discoveries. Use when starting or resuming multi-session work tracked in a plan file.

SKILL.md

2.2 KB, as published. Nobody here has run it

Work on TPP

Documented in depth: Claude Code has amnesia. So do PRs, changelogs, and your future self.

A Technical Project Plan (TPP) is a living handoff document: it carries research, design decisions, failed approaches, and next steps across sessions, so the next session (or the next engineer) continues instead of restarting.

Make progress on the referenced TPP. Determine the current phase and take appropriate action.

Required Reading First

Before any work, you MUST read:

The project's instructions: AGENTS.md, plus CLAUDE.md when present
The project's TPP guide: docs/TPP-GUIDE.md if it exists; otherwise the bundled reference TPP-GUIDE.md

Process

Read the referenced TPP. It will live in _todo/, in a priority folder (_active/, _p1/…_p4/), or in a documented feature integration queue matching _feat-<name>/ if this project uses them.
Identify the current phase.
Do the work for that phase.
Update the TPP with progress and discoveries — gotchas, rejected approaches, and the why behind decisions, not a transcript.

When context runs low before the work is done, invoke the handoff skill rather than letting the session end silently. When the TPP is complete, move it to _done/.

Adapting for your project

Create a project docs/TPP-GUIDE.md (start from the bundled reference) and tailor the layout, frontmatter fields, and template to your conventions — the project guide always takes precedence over the bundled copy.
Extend the required reading list with your high-value docs (DESIGN-PRINCIPLES.md, TDD.md, architecture decisions). Every listed file is read on every invocation, so keep it short.
Automate durable reminders portably. Put the TPP update requirement in the repository's AGENTS.md, or use a supported project hook or automation that prompts the coding agent to update the active TPP before a task ends.