office-pdca-workflow

Classify CT_office tasks and generate PDCA documents with devlog handoff checks.

Updated Mar 3, 2026
One-click install
npx skills add https://github.com/createtree2017/createtree-office --skill office-pdca-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: office-pdca-workflow
Source: https://github.com/createtree2017/createtree-office/tree/main/.agents/skills/office-pdca-workflow
Command: npx skills add https://github.com/createtree2017/createtree-office --skill office-pdca-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

CT_office work often gets documented inconsistently, making it hard to classify tasks, validate progress, and hand off the right Plan/Design/Check/Report/devlog materials reliably.

Core Features & Use Cases

  • PDCA document selection & task classification: Assigns work into Quick Fix, Minor Change, Feature, or Major Feature based on scope and risk.
  • Consistency rules for development handoff: Ensures Feature-or-higher work has relevant Plan/Design and that code changes trigger the correct docs/05-devlog/ handoff when needed.
  • Documentation governance: Keeps date/filename conventions aligned with GEMINI.md and updates SKILLS_INDEX.md if PDCA storage, state values, validation commands, or handoff format change.

Quick Start

Use the office-pdca-workflow guideline to draft the appropriate Plan/Design/Check/Report/devlog set for your CT_office task while following the GEMINI.md naming rules and devlog handoff triggers.

Frequently Asked Questions about office-pdca-workflow

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

FAQPage Schema
How do I standardize PDCA documentation for development handoff?

Standardize PDCA documentation by classifying tasks into Quick Fix, Minor Change, Feature, or Major Feature levels, then validating required Plan/Design artifacts and triggering devlog handoffs for code changes to ensure consistent engineering workflow deliverables.

What is the best way to classify engineering tasks for PDCA reporting?

Classify engineering tasks by scope and risk into Quick Fix, Minor Change, Feature, or Major Feature categories. This PDCA task classification determines the required validation steps, Plan/Design documentation depth, and whether a devlog handoff document is mandated.

When do I need a devlog handoff document for my code changes?

You need a devlog handoff document when your PDCA task includes code changes. The workflow requires generating handoff documents in the docs/05-devlog/ directory to ensure consistent development handoff and implementation completion reporting for code-including tasks.

Does this PDCA workflow require Plan and Design validation for Feature changes?

Yes, this PDCA workflow requires Plan and Design validation for any Feature-or-higher changes. It ensures engineering workflow consistency by mandating relevant Plan/Design artifacts before implementation, securing proper documentation governance for higher-risk tasks.

How do I keep date and filename conventions aligned with GEMINI.md rules?

Keep date and filename conventions aligned with GEMINI.md by applying PDCA documentation governance rules. The workflow updates SKILLS_INDEX.md whenever storage, state values, validation commands, or devlog handoff formats change to maintain documentation consistency.

Can I use this workflow for quick fixes without generating full Plan and Design documents?

Yes, you can use this workflow for Quick Fix tasks without full Plan and Design documents. The PDCA artifact selection scales by task size and risk, meaning lower-level classifications require significantly less documentation overhead than Feature-or-higher changes.