Project Template

Creates a shared project hub tracking issues, ideas, PRs, and session handovers across agent sessions.

1|1|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/PostHog/community-skills --skill project-template-posthog
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Project Template
Source: https://github.com/PostHog/community-skills/tree/main/skills/project-template
Command: npx skills add https://github.com/PostHog/community-skills --skill project-template-posthog

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Ongoing work spread across many agent sessions and people loses context: issues get re-diagnosed, handovers get clobbered, and durable facts disappear. This Skill provides a living project hub that agents and people share, so every session resumes with full state and logs its work before ending. ## Core Features & Use Cases - Numbered backlog: One file per issue and idea with status indexes, so work items are citable by number and never re-diagnosed. - Session handover protocol: A sectioned HANDOVER.md each session overwrites, plus a rolling-window CHANGELOG.md trimmed on every write. - Durable memory files: environment-notes.md for gotchas, field-feedback.md for user signals, open-prs.md audited against GitHub, and roadmap.md for ordering rationale. - Use Case: Install it once per workstream (e.g. billing), then ask an agent to log an issue, resume work in a fresh session, or triage the backlog without losing prior context. ## Quick Start Install the project-template skill, bind your project name, and ask the agent to set up the hub and log the first issue for your workstream.

Frequently Asked Questions about Project Template

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

FAQPage Schema
How do I track ongoing project work across multiple agent sessions?▼

Install this skill once per workstream and bind the project name. Each session reads HANDOVER.md and the issues index on resume, then logs issues, PRs, and a changelog line before ending, so the next session inherits full context.

How do I set up the project hub after installing the skill?▼

Follow the SETUP.md checklist in the first session: rename the skill, rewrite the description for retrieval, seed issues and environment notes, configure open-prs.md with your repo, then delete SETUP.md and add a changelog line.

What tools does this skill require to work?▼

It runs over the PostHog MCP skill-* tools: skill-get, skill-list, skill-file-get, skill-update, skill-file-create, skill-file-delete, and skill-file-rename. Any agent connected to the PostHog MCP can use it.

Where should durable facts go instead of the changelog?▼

Durable facts belong in environment-notes.md, which is never clobbered. The changelog is a rolling window of one-line entries trimmed on every write, so detail placed there is eventually dropped.

Can I use one hub for multiple areas of work?▼

No, the template recommends one hub per area. Install the skill again under another name for a second workstream and cross-link the two hubs, citing issues by hub name and number rather than renumbering.