ocp-phase-docs

Update project documentation files after completing a development phase.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/rnny66/OPC --skill ocp-phase-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ocp-phase-docs
Source: https://github.com/rnny66/OPC/tree/main/.claude/skills/ocp-phase-docs
Command: npx skills add https://github.com/rnny66/OPC --skill ocp-phase-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the crucial post-phase documentation update process, ensuring all project records are current and comprehensive.

Core Features & Use Cases

  • Comprehensive Documentation Update: Ensures all relevant project documents (plans, functional docs, technical docs, CLAUDE.md, skills, MEMORY.md) are updated after each development phase.
  • Phase Completion Tracking: Facilitates clear marking of completed tasks and deferred items in phase plans.
  • Use Case: After completing Phase 2 of the OPC platform development, use this skill to systematically update the phase plan, functional documentation for new features, technical architecture diagrams, and the main CLAUDE.md file.

Quick Start

Use the ocp-phase-docs skill to update all project documentation after completing a platform phase.

Frequently Asked Questions about ocp-phase-docs

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

FAQPage Schema
How do I update project documentation after completing a development phase?

Updating project documentation after a development phase requires manually reviewing and modifying markdown files like phase plans, functional docs, technical docs, CLAUDE.md, and MEMORY.md to reflect phase deliverables and ensure knowledge base consistency.

What is the best way to track phase completion in project plans?

Tracking phase completion in project plans involves systematically marking completed tasks and deferred items within the phase plan documentation, ensuring project records accurately reflect current development progress and outstanding deliverables.

Does this documentation update process work without automated scripts?

Yes, the documentation update process works without automated scripts because it requires manual review and targeted updates to specific markdown files based on phase deliverables, ensuring comprehensive knowledge base consistency without automated generation.

How do I maintain consistency across functional and technical documentation?

Maintaining consistency across functional and technical documentation requires systematically updating all project records, including functional docs and technical architecture diagrams, after each development phase concludes to keep the knowledge base comprehensive.

What files need to be updated for a complete project knowledge base refresh?

A complete project knowledge base refresh requires updating phase plans, functional documentation, technical documentation, CLAUDE.md, skills, and MEMORY.md to ensure all records remain current and comprehensive after a development phase.

When should I update CLAUDE.md and MEMORY.md in my project workflow?

You should update CLAUDE.md and MEMORY.md in your project workflow immediately after a development phase is completed, ensuring all project knowledge bases reflect the latest phase deliverables and maintain overall consistency.