skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
ww-w-ai/bkit-claude-code56 installs

bkit-templates

PDCA + Sprint document templates — Plan, Design, Analysis, Report for individual features plus templates/sprint/{master-plan, prd, plan, design, iterate, qa, report}.template.md for sprint-level documents (v2.1.13). Triggers: template, plan document, design template

How do I install this agent skill?

npx skills add https://github.com/ww-w-ai/bkit-claude-code --skill bkit-templates
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The skill provides a set of templates and guidelines for PDCA and Sprint documentation. It uses standard file-reading tools and contains no malicious code, external dependencies, or obfuscation.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

What does this agent skill do?

bkit Document Templates

Use these templates when generating PDCA documents.

Available Templates

PDCA (per-feature, 9-phase)

TemplatePathPurpose
Plan${CLAUDE_PLUGIN_ROOT}/templates/plan.template.mdFeature planning
Design${CLAUDE_PLUGIN_ROOT}/templates/design.template.mdTechnical design
Analysis${CLAUDE_PLUGIN_ROOT}/templates/analysis.template.mdGap analysis
Report${CLAUDE_PLUGIN_ROOT}/templates/report.template.mdCompletion report
Index${CLAUDE_PLUGIN_ROOT}/templates/_INDEX.template.mdDocument index
CLAUDE${CLAUDE_PLUGIN_ROOT}/templates/CLAUDE.template.mdCLAUDE.md template

Sprint (multi-feature container, 8-phase, v2.1.13)

TemplatePathPurpose
Master Plan${CLAUDE_PLUGIN_ROOT}/templates/sprint/master-plan.template.mdSprint scope + features + dependency graph + Trust scope
PRD${CLAUDE_PLUGIN_ROOT}/templates/sprint/prd.template.mdSprint-level product requirements
Plan${CLAUDE_PLUGIN_ROOT}/templates/sprint/plan.template.mdSprint plan (per-feature plan synthesis)
Design${CLAUDE_PLUGIN_ROOT}/templates/sprint/design.template.mdSprint-level technical design
Iterate${CLAUDE_PLUGIN_ROOT}/templates/sprint/iterate.template.mdIteration log + iterateHistory
QA${CLAUDE_PLUGIN_ROOT}/templates/sprint/qa.template.md7-Layer dataFlowIntegrity (S1) report
Report${CLAUDE_PLUGIN_ROOT}/templates/sprint/report.template.mdSprint completion + KPI + carry items

Template Usage

Plan Template

For Plan phase - feature planning before design.

Key sections:

  • Overview & Purpose
  • Scope (In/Out)
  • Requirements (Functional/Non-Functional)
  • Success Criteria
  • Risks & Mitigation

Design Template

For Do phase - technical design before implementation.

Key sections:

  • Architecture (diagrams, data flow)
  • Data Model (entities, relationships)
  • API Specification (endpoints, request/response)
  • UI/UX Design (layouts, components)
  • Error Handling
  • Security Considerations
  • Test Plan
  • Implementation Guide

Analysis Template

For Check phase - gap analysis between design and implementation.

Key sections:

  • Design vs Implementation comparison
  • Missing features
  • Inconsistencies
  • Quality metrics
  • Recommendations

Report Template

For Act phase - completion report and lessons learned.

Key sections:

  • Summary of completed work
  • Metrics (LOC, test coverage, etc.)
  • Issues encountered
  • Lessons learned
  • Future improvements

Document Output Paths

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

Variable Substitution

Templates use {variable} syntax:

  • {feature}: Feature name
  • {date}: Creation date (YYYY-MM-DD)
  • {author}: Document author

Pipeline Templates

Additional templates for Development Pipeline phases:

  • ${CLAUDE_PLUGIN_ROOT}/templates/pipeline/ directory

Document Standards

File Naming Rules

{number}_{english_name}.md      # 01_system_architecture.md
{number}-{english_name}.md      # 01-system-architecture.md
{feature}.{type}.md             # login.design.md

Common Header

All documents should include:

# {Document Title}

> **Summary**: {One-line description}
>
> **Author**: {Name}
> **Created**: {YYYY-MM-DD}
> **Last Modified**: {YYYY-MM-DD}
> **Status**: {Draft | Review | Approved | Deprecated}

---

Version Control

Track changes within documents:

## Version History

| Version | Date | Changes | Author |
|---------|------|---------|--------|
| 1.0 | 2024-12-01 | Initial draft | Kay |
| 1.1 | 2024-12-05 | Added API spec | Kay |

Cross-References

Link related documents:

## Related Documents
- Plan: [login.plan.md](../01-plan/features/login.plan.md)
- Design: [login.design.md](../02-design/features/login.design.md)
- Analysis: [login.analysis.md](../03-analysis/features/login.analysis.md)

Status Tracking

Use _INDEX.md in each folder:

StatusMeaningClaude Behavior
✅ ApprovedUse as referenceFollow as-is
🔄 In ProgressBeing writtenNotify of changes
⏸️ On HoldTemporarily pausedRequest confirmation
❌ DeprecatedNo longer validIgnore

Conflict Resolution

  • Code vs Design mismatch: Code is truth, suggest document update
  • Multiple versions: Reference only the latest version

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/ww-w-ai/bkit-claude-code/bkit-templates">View bkit-templates on skillZs</a>