develop

Enforce governance rules for plan-package execution and knowledge-base updates.

1|Updated Nov 21, 2025
One-click install
npx skills add https://github.com/bamecho/my-claude-skills --skill develop-bamecho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: develop
Source: https://github.com/bamecho/my-claude-skills/tree/main/skills/HelloAgents/develop
Command: npx skills add https://github.com/bamecho/my-claude-skills --skill develop-bamecho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Development Implementation phase governs and enforces detailed rules when a plan package enters execution, ensuring code changes are carried out systematically, knowledge bases are refreshed, and deliverables are migrated to history.

Core Features & Use Cases

  • Enforced pre-checks and gated approvals before any development tasks commence.
  • Step-by-step execution protocol including plan reading, file changes, and consistency audits.
  • Knowledge base synchronization and plan package migration to history to maintain traceability.

Quick Start

Initialize a plan package in plan/YYYYMMDDHHMM_<feature> and start the development implementation workflow.

Frequently Asked Questions about develop

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

FAQPage Schema
How do I enforce coding standards during a development implementation phase?

To enforce coding standards during the development implementation phase, this Skill applies gated approvals and step-by-step execution protocols. It automatically audits file changes against established rules before allowing deliverables to migrate.

What is a plan package and when do I need it for code migration?

A plan package is a structured directory, formatted as plan/YYYYMMDDHHMM_<feature>, containing execution details. You need it before starting development to trigger mandatory pre-checks, consistency audits, and artifact migration to history.

How to maintain knowledge-base traceability after performing code changes?

Maintain knowledge-base traceability by enforcing mandatory knowledge-base updates after code changes. This Skill governs the workflow by synchronizing the knowledge base and migrating completed plan packages to history with rollback safeguards.

Does the development implementation workflow require a specific directory structure?

Yes, the workflow requires a defined plan package structured in the plan/ directory. Without this specific plan package format, the strict transition checks and gated approvals cannot commence.

What are the limitations of automating development governance without pre-checks?

Without enforced pre-checks, development governance fails to ensure systematic code changes and traceability. Bypassing these gated approvals risks inconsistent knowledge bases and losing rollback safeguards during artifact migration.

Why does code migration to history require consistency audits?

Code migration to history requires consistency audits to ensure all file changes align with the original plan package. This strict transition check maintains traceability and validates that knowledge-base updates are accurately synchronized.