PDCA document templates for consistent documentation. Plan, Design, Analysis, and Report templates with proper structure.
/plugin marketplace add popup-studio-ai/bkit-claude-code/plugin install bkit@bkit-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Use these templates when generating PDCA documents.
| Template | Path | Purpose |
|---|---|---|
| Plan | ${CLAUDE_PLUGIN_ROOT}/templates/plan.template.md | Feature planning |
| Design | ${CLAUDE_PLUGIN_ROOT}/templates/design.template.md | Technical design |
| Analysis | ${CLAUDE_PLUGIN_ROOT}/templates/analysis.template.md | Gap analysis |
| Report | ${CLAUDE_PLUGIN_ROOT}/templates/report.template.md | Completion report |
| Index | ${CLAUDE_PLUGIN_ROOT}/templates/_INDEX.template.md | Document index |
| CLAUDE | ${CLAUDE_PLUGIN_ROOT}/templates/CLAUDE.template.md | CLAUDE.md template |
For Plan phase - feature planning before design.
Key sections:
For Do phase - technical design before implementation.
Key sections:
For Check phase - gap analysis between design and implementation.
Key sections:
For Act phase - completion report and lessons learned.
Key sections:
docs/
├── 01-plan/
│ └── features/
│ └── {feature}.plan.md
├── 02-design/
│ └── features/
│ └── {feature}.design.md
├── 03-analysis/
│ └── features/
│ └── {feature}.analysis.md
└── 04-report/
└── features/
└── {feature}.report.md
Templates use {variable} syntax:
{feature}: Feature name{date}: Creation date (YYYY-MM-DD){author}: Document authorAdditional templates for Development Pipeline phases:
${CLAUDE_PLUGIN_ROOT}/templates/pipeline/ directoryThis skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.