pdca

Automate PDCA cycle management and generate Plan, Design, Analysis, and Report artifacts.

Updated Feb 2, 2026
One-click install
npx skills add https://github.com/joshua3403/giit-template --skill pdca
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pdca
Source: https://github.com/joshua3403/giit-template/tree/main/.agent/skills/pdca
Command: npx skills add https://github.com/joshua3403/giit-template --skill pdca

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the end-to-end PDCA cycle management, enabling teams to plan, design, implement, analyze, and report with consistent artifacts and traceable progress.

Core Features & Use Cases

  • Plan/Design/Do/Check/Act workflow automation using pre-defined templates and task generation.
  • Auto-triggered prompts from keywords (plan, design, analyze, report, status) to guide conversations and document creation.
  • Reproducible PDCA artifacts (plans, designs, analyses, and reports) that can be archived or reviewed.

Quick Start

Use the PDCA skill by issuing phase commands such as /pdca plan <feature>, /pdca design <feature>, /pdca analyze <feature>, /pdca report <feature>.

Frequently Asked Questions about pdca

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

FAQPage Schema
How do I automate the PDCA cycle for product planning and analysis?

Yes, workflow automation can be triggered using keywords like plan, design, analyze, and report, which automatically guide conversations and generate the corresponding PDCA artifacts for your engineering or operations teams.

Does this PDCA workflow automation support operations and engineering teams?

Yes, the PDCA workflow automation applies directly to product teams, engineering, and operations, enabling them to plan, implement, analyze, and report with consistent artifacts and traceable progress.

How do I generate consistent documentation for the Plan and Do phases?

You can generate consistent documentation by using the /pdca plan and /pdca design commands, which rely on in-repo templates to produce reproducible artifacts that can be archived or reviewed later.

Are there limitations to using pre-defined templates for PDCA iteration and reporting?

The main limitation is that the PDCA iteration and reporting rely on pre-defined in-repo templates, meaning the generated artifacts follow a fixed structure rather than offering highly customized formatting.