ph

Creates handover documents with progress, context, and next steps for developers.

12|2|Updated Nov 20, 2025

Search Tags:#workflow #documentation #codebase #handover #task continuation #developer handoff

Ready to run

npx skills add https://github.com/alexandrbasis/wythm-claude-workflows --skill ph

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ph
Source: https://github.com/alexandrbasis/wythm-claude-workflows/tree/main/.claude/skills/ph
Command: npx skills add https://github.com/alexandrbasis/wythm-claude-workflows --skill ph

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that development work can be seamlessly handed over to another developer by creating comprehensive and self-contained documentation at logical breakpoints.

Core Features & Use Cases

Codebase Continuity: Prevents knowledge silos and lost progress by documenting the current state of a task.
Onboarding Acceleration: Enables new or unfamiliar developers to quickly understand and continue ongoing work.
Use Case: A developer is working on a complex feature and needs to hand it off for a code review or to another team member. This Skill generates a document detailing the progress, technical context, and next steps, allowing the next developer to pick up exactly where they left off.

Quick Start

Use the ph skill to prepare handover documentation for the current task.

Frequently Asked Questions about ph

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

FAQPage Schema

How do I prepare handover documentation for developer task continuation?▼

Developer handoff documentation covers problem statements, current progress, technical context, file locations, execution instructions, and known issues. This creates a self-contained, newcomer-friendly task document enabling seamless developer handoffs and immediate task continuation.

How do I document codebase progress for a seamless developer handoff?▼

Documenting codebase progress involves stopping at a logical implementation breakpoint and recording the problem statement, technical context, and recommended next steps. This creates a newcomer-friendly task document that prevents knowledge silos and enables another developer to pick up exactly where you left off.

What is included in developer handoff documentation for codebase continuity?▼

Developer handoff documentation includes the problem statement, current progress, technical context, file locations, execution instructions, known issues, and recommended next steps. This self-contained document prevents lost progress and accelerates onboarding for unfamiliar developers continuing the task.

Can I generate task continuation documents at any point in my workflow?▼

You can generate task continuation documents at logical implementation breakpoints within your workflow. Creating the handover documentation at these stopping points ensures the document accurately reflects the current codebase state and provides clear execution instructions for the next developer.

What is the best way to create newcomer-friendly handover documentation for a code review?▼

The best way to create newcomer-friendly handover documentation is to compile a self-contained task document covering technical context, file locations, and known issues. This details your progress and recommended next steps, allowing the reviewer or new team member to quickly understand ongoing work.