writing-execution-prompts

Name: writing-execution-prompts
Availability: InStock
Author: michaelkd01

Formalize Claude Code prompt creation with required sections and validation rules.

Updated Aug 27, 2026

Search Tags:#claude-code #execution-prompts #branch-workflow #prompt-standards #test-contract #verification-checklist

Ready to run

npx skills add https://github.com/michaelkd01/dic-skills --skill writing-execution-prompts

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: writing-execution-prompts
Source: https://github.com/michaelkd01/dic-skills/tree/main/writing-execution-prompts
Command: npx skills add https://github.com/michaelkd01/dic-skills --skill writing-execution-prompts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures every Claude Code execution prompt follows a uniform format with mandatory sections so scoping, testing, verification, and commit guidance never get omitted.

Core Features & Use Cases

Structure enforcement: Mandates Title, Context, Test Contract, Instructions, Verification, Commit & Push, and Rules sections in every prompt so Claude Code receives complete instructions.
Validation guardrails: Requires reporting command outputs, running prescribed verification steps, and observing branch naming plus git identity rules to keep deliverables auditable.
Use case: A pre-planner drafting a pipeline task prompt can rely on this skill to produce a ready-to-run instruction set that Claude Code will execute without ambiguity.

Quick Start

Ask the skill to draft a Claude Code prompt for implementing a new API feature while following the required structure and validation checklist.

Frequently Asked Questions about writing-execution-prompts

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

FAQPage Schema

How do I standardize Claude Code prompts for branch workflows?▼

Standardize Claude Code prompts by enforcing mandatory sections like Title, Context, Test Contract, Instructions, Verification, and Commit Rules to ensure consistent task execution. This structure guarantees Claude Code receives complete, unambiguous instructions for pipeline tasks and scaffolds.

What is a test contract in Claude Code execution prompts?▼

A test contract in execution prompts is a mandatory section specifying the verification steps and command outputs Claude Code must report. It ensures deliverables remain auditable by requiring prescribed verification checks before completing the task.

How do I write Claude Code instructions for API feature scaffolding?▼

Write Claude Code instructions for API scaffolding by drafting a prompt with required sections: Title, Context, Test Contract, Instructions, Verification, and Commit details. This ready-to-run format eliminates ambiguity during feature implementation.

Does this prompt standardization approach require specific git branch rules?▼

Yes, the prompt standardization requires observing branch naming conventions and git identity rules. These branch rules are specified in the prompt structure to keep deliverables auditable and ensure consistent commit guidance.

Why do my Claude Code pipeline tasks fail to execute consistently?▼

Claude Code pipeline tasks fail consistently when prompts omit mandatory sections like context, test contracts, or verification steps. Formalizing prompt creation guidelines ensures scoping, testing, and commit guidance are never omitted, preventing execution failures.