← ChatPRDCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to ChatPRD
Snapshot Oct 9, 2026 · 18:02 UTC · version 1.2.5
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Fetch a PRD from ChatPRD and generate a scoped implementation plan for the current code repository. Use in a coding workspace when starting work on a spec, breaking down a PRD into tasks, or planning how to build a feature.",
"included_files": [],
"name": "implement-from-prd",
"skill_md_contents": "---\nname: implement-from-prd\ndescription: Fetch a PRD from ChatPRD and generate a scoped implementation plan for the current code repository. Use in a coding workspace when starting work on a spec, breaking down a PRD into tasks, or planning how to build a feature.\n---\n\n# Implement from PRD\n\n## Trigger\n\nUser has a PRD in ChatPRD and wants to plan or start the implementation.\n\n## Workflow\n\n1. Help the user find the right PRD:\n - Search documents using `search_documents` if they give a name or keyword.\n - Or list recent documents using `list_documents` to browse.\n - Also check the local `prd/` directory for previously saved specs.\n2. Fetch the full PRD content using `get_document`.\n3. Build the implementation plan before writing code (use plan mode if your editor has one). The plan should:\n - Analyze the codebase to understand where new code should live, what can be reused, and what conventions to follow.\n - Break the PRD into implementation milestones, each a shippable increment ordered by dependency (schema → API → UI).\n - For each milestone, specify: files to create or modify, key implementation details, acceptance criteria from the PRD, and risks or unknowns.\n - Map every PRD requirement to at least one milestone so nothing is missed.\n4. Present the plan for the user to review and approve before starting implementation.\n5. Once approved, begin work on the first milestone.\n\n## Guardrails\n\n- Always plan first — never jump straight to implementation on a PRD.\n- Map every PRD requirement to at least one milestone.\n- Flag requirements that are ambiguous or missing technical detail.\n- Keep milestones small enough to review in a single PR.\n- Don't skip edge cases mentioned in the PRD.\n\n## Output\n\n- Implementation plan with ordered milestones\n- File-level change list per milestone\n- Requirement coverage mapping\n- Ready to execute on first milestone after approval\n"
}SHA-256 of public snapshot: 07ac8c7417f85a7606687c720d4415974c2187eea134914c9ba4243c576aa156