How do I install the Plan Validate Execute Template skill?

Run npx skillmds add majiayu000/plan-validate-execute-template in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Plan Validate Execute Template safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Plan Validate Execute Template?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Plan Validate Execute Template free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Plan Validate Execute Template?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Plan Validate Execute Template by majiayu000

Name: Plan Validate Execute Template
Rating: 4.5 (4 reviews)
Author: majiayu000

File contents

name: plan-validate-execute-template description: [REPLACE] Plan changes, validate before execution, execute with verification. Use when [REPLACE with specific triggers]. allowed-tools: Read, Write, Edit, Grep, Glob, Bash, TodoWrite

Plan-Validate-Execute Template

Purpose

This template demonstrates the Plan → Validate → Execute → Verify workflow for operations requiring approval gates and validation.

Use this template when:

Changes are irreversible or high-risk
User approval needed before execution
Validation required before and after changes
Rollback procedures necessary

Workflow

Phase 1: Plan

Phase 2: Validate Plan

Phase 3: Execute

Phase 4: Verify

Progressive Disclosure

Core workflow (this file):

Plan → Validate → Execute → Verify phases
Approval gates and checkpoints

Detailed guidance (references/):

references/migration-example.md - Complete database migration
Rollback procedures and error handling

Example Usage

<plan>
Migration Plan: Users table normalization
1. Create new addresses table
2. Migrate address data
3. Add foreign keys
4. Drop old columns
Estimated time: 5 minutes
Risk: Medium (data transformation)
Rollback: Restore from backup
</plan>

<validate-plan>
✓ Sample data transformation verified
✓ Foreign key constraints tested
✓ Rollback procedure confirmed
⚠️ Awaiting user approval to proceed
</validate-plan>

<execute>
[Step 1/4] Creating addresses table... ✓
[Step 2/4] Migrating 1,245 records... ✓
[Step 3/4] Adding foreign keys... ✓
[Step 4/4] Dropping old columns... ✓
</execute>

<verify>
✓ All 1,245 records migrated successfully
✓ Foreign key constraints valid
✓ No orphaned records
✓ Application tests passing
Migration complete!
</verify>

---name: plan-validate-execute-templatedescription: [REPLACE] Plan changes, validate before execution, execute with verification. Use when [REPLACE with specific triggers].--- --- name: plan-validate-execute-template description: [REPLACE] Plan changes, validate before execution, execute with verification. Use when [REPLACE with specific triggers]. allowed-tools: Read, Write, Edit, Grep, Glob, Bash, TodoWrite --- # Plan-Validate-Execute Template ## Purpose This template demonstrates the Plan → Validate → Execute → Verify workflow for operations requiring approval gates and validation. **Use this template when:** - Changes are irreversible or high-risk - User approval needed before execution - Validation required before and after changes - Rollback procedures necessary ## Workflow ### Phase 1: Plan <plan> 1. Analyze current state 2. Define desired end state 3. Break down into atomic steps 4. Identify risks and dependencies 5. Create rollback plan 6. Present plan for approval </plan> ### Phase 2: Validate Plan <validate-plan> 1. Check preconditions 2. Verify dependencies exist 3. Test transformations on sample data 4. Confirm rollback procedure works 5. Get explicit user approval before proceeding </validate-plan> ### Phase 3: Execute <execute> 1. Create backup/checkpoint 2. Execute steps sequentially 3. Log each operation 4. Stop on first error 5. Provide progress updates </execute> ### Phase 4: Verify <verify> 1. Confirm all changes applied 2. Run validation tests 3. Check data integrity 4. Verify system functionality 5. Document completion </verify> <validate> Run the following validation script: `/scripts/validate-skill-output.sh {arguments}` </validate> ## Progressive Disclosure **Core workflow (this file):** - Plan → Validate → Execute → Verify phases - Approval gates and checkpoints **Detailed guidance (references/):** - references/migration-example.md - Complete database migration - Rollback procedures and error handling ## Example Usage ```xml <plan> Migration Plan: Users table normalization 1. Create new addresses table 2. Migrate address data 3. Add foreign keys 4. Drop old columns Estimated time: 5 minutes Risk: Medium (data transformation) Rollback: Restore from backup </plan> <validate-plan> ✓ Sample data transformation verified ✓ Foreign key constraints tested ✓ Rollback procedure confirmed ⚠️ Awaiting user approval to proceed </validate-plan> <execute> [Step 1/4] Creating addresses table... ✓ [Step 2/4] Migrating 1,245 records... ✓ [Step 3/4] Adding foreign keys... ✓ [Step 4/4] Dropping old columns... ✓ </execute> <verify> ✓ All 1,245 records migrated successfully ✓ Foreign key constraints valid ✓ No orphaned records ✓ Application tests passing Migration complete! </verify> ``` ## See Also - @references/migration-example.md - Full migration workflow

Frequently asked questions