develop

Orchestrate development execution with pre-checks, sequencing, and migration to history.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill defines and enforces the development execution phase, ensuring required plan packages exist, pre-checks verify legality, and changes are auditable through a deterministic workflow, with safeguards for backups and rollback.

Core Features & Use Cases

  • Pre-checks and gating: Validates required plan packages exist and routing conditions are met.
  • Execution orchestration: Sequences plan steps, updates task statuses, and logs outcomes for deterministic delivery.
  • Migration and auditing: Safely migrates completed packages to history, keeps knowledge bases in sync, and performs consistency checks for traceability.
  • Backup and rollback: Encourages backups before changes and provides rollback guidance in case of failures.

Quick Start

Identify a complete plan under plan/, ensure plan.md and why.md exist, then trigger the development execution flow through Claude Code with this skill activated. Follow prompts to select the plan package if multiple exist, execute tasks as defined in task.md, and migrate the completed package to history/ upon successful completion.

Frequently Asked Questions about develop

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

FAQPage Schema
How do I enforce pre-checks and validation before executing a development plan?

Development execution pre-checks validate that a complete plan package exists in plan/ with required plan.md and why.md files. This gating ensures routing conditions are met and changes are auditable before executing multi-step tasks defined in task.md.

What is the best way to sequence multi-step development tasks and update their status?

Execution orchestration sequences plan steps defined in task.md, updates task statuses dynamically, and logs outcomes for deterministic delivery. This standardized workflow ensures every executed step is tracked and traceable throughout the development execution phase.

Do I need a specific folder structure to start a development execution workflow?

Yes, you need a complete plan package under the plan/ directory containing both plan.md and why.md files. The execution flow requires this structure to validate the plan and route multi-step tasks before initiating any development changes.

How do I migrate completed development packages to history for auditing?

After successful task completion, the workflow safely migrates the finished package to a history/ directory. It keeps knowledge bases in sync and performs consistency checks to ensure full traceability and traceable audits for the completed development work.

Can I rollback changes if a development execution step fails?

Yes, the workflow encourages backups before applying changes and provides rollback guidance in case of failures. Strict safety and quality checks are enforced before execution to minimize failure risk and support safe recovery during development.