ptp

Routes ptp commands and policies to their owning files.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/AlmogMaayan/ptp --skill ptp-almogmaayan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ptp
Source: https://github.com/AlmogMaayan/ptp/tree/main/skills/ptp
Command: npx skills add https://github.com/AlmogMaayan/ptp --skill ptp-almogmaayan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working with the PtP change pipeline, it is hard to know which file owns each /ptp:* command or policy. This Skill acts as a router that maps every command and policy to the single file that defines its behavior, so you always read the authoritative source instead of guessing. ## Core Features & Use Cases - Command Routing: Maps every /ptp:* command (brainstorm, plan, apply, review, archive, deploy, telemetry, and more) to the command file or skill that owns its contract. - Policy Ownership: Identifies the single file carrying each indexed policy, such as branch safety, model dispatch, codex mode resolution, and terminal states. - Use Case: You want to know how /ptp:review-loop behaves. Instead of reading dozens of files, consult this router, which points you to skills/ptp-review-loop/SKILL.md as the owner of both the command and the review severity policy. ## Quick Start Ask which file owns the /ptp:full command and read that owning file for its behavior.

Frequently Asked Questions about ptp

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

FAQPage Schema
How do I find which file owns a ptp command?▼

Consult the command routing table in this skill, which maps each `/ptp:*` command to its owning file. Commands owned by a skill are thin front doors that parse arguments and invoke that skill; self-owned commands carry their own contract.

What is the ptp router skill used for?▼

It routes ptp requests by naming the file that owns each command and each indexed policy. It states no behavior itself, so you read the owning file for steps, variants, and terminal states.

Where are ptp policies like branch safety defined?▼

Each policy lives as a section in exactly one file. For example, branch safety is owned by `skills/ptp-branch-guard/SKILL.md` and model dispatch by `skills/ptp-run-at-model/SKILL.md`.

Does the ptp router skill execute any pipeline steps?▼

No. The router only names owning files and contains no steps, variants, or terminal states. All execution behavior is defined in the owning command or skill file it points to.

Can two files define the same ptp policy?▼

No. Each indexed policy is carried as a section of that name by exactly one file, and no other file under commands, skills, or agents may carry that section heading.