skills.rest
hellowind777
hellowind777COMMUNITY
Explore all skills by this author →
GitHub

develop

Enforce development phase rules for plan package execution and knowledge synchronization.

654|94|Updated Sep 26, 2025
Search Tags:#workflow#planning#development#migration#code-quality#knowledge-base
One-click install
npx skills add https://github.com/hellowind777/helloagents --skill develop-hellowind777
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: develop
Source: https://github.com/hellowind777/helloagents/tree/main/Archive/1.x/Claude/Skills/CN/skills/helloagents/develop
Command: npx skills add https://github.com/hellowind777/helloagents --skill develop-hellowind777

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates and enforces the development implementation phase rules to ensure compliant code changes and smooth knowledge-base migrations.

Core Features & Use Cases

  • Enforces mandatory preconditions before development execution and ensures traceable decision gates.
  • Orchestrates plan package validation, execution steps, knowledge-base synchronization, and migration to history.
  • Provides audit-ready output and guidance for safe rollbacks and recovery in development workflows.

Quick Start

Apply the develop rules to a plan package entering the development phase to start the workflow.

Frequently Asked Questions about develop

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

FAQPage Schema
How do I enforce preconditions and decision gates during a development implementation workflow?▼

A development implementation workflow enforces preconditions by validating predefined plan packages, checking strict gating conditions, and ensuring structured YAML frontmatter before executing code changes.

What is automated knowledge-base synchronization in a development workflow?▼

Automated knowledge-base synchronization updates documentation and audit trails during code execution, ensuring project knowledge stays compliant and traceable when plan packages migrate to history.

How do I start a rule-based development execution phase from an existing plan package?▼

To start a rule-based development execution phase, apply the automated workflow rules to a plan package entering the implementation stage to trigger pre-checks, code hygiene, and changelog updates.

Can I use structured YAML frontmatter to validate code changes in a development workflow?▼

Yes, structured YAML frontmatter is required to validate compliant code changes, acting as a strict gating condition to ensure traceable decision gates and audit-ready output.

What is the best way to migrate completed plan packages to history while maintaining an audit trail?▼

The best way to migrate completed plan packages to history uses integration hooks to automatically update changelogs, synchronize the knowledge base, and preserve a safe rollback audit trail.

When do I need strict gating conditions for code changes and knowledge-base migration?▼

Strict gating conditions are needed when a plan package enters the development implementation stage, ensuring compliant code changes, safe rollbacks, and structured documentation before migration.

Related Skills

Explore More Software Engineering Skills→
reggiechan74reggiechan74
5

Acceptance Criteria

Define testable acceptance criteria with YAML templates and validator roles before code execution.

Community
Basic
marqus0004marqus0004

doc-sync

Synchronize repository documentation across CLAUDE.md and README.md indexes.

Community
Intermediate
prototypdigitalprototypdigital

docs-upkeep

Update and validate documentation alongside code changes within version control workflows.

Official
Advanced
SocketDevSocketDev
43

release

Automates release workflows with quality/security scans, changelog generation, and version bumping.

Official
Intermediate