prompt-engineering-anatomy-of-a-prompt
Sub-skill of prompt-engineering: Anatomy of a Prompt (+1).
Best use case
prompt-engineering-anatomy-of-a-prompt is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of prompt-engineering: Anatomy of a Prompt (+1).
Teams using prompt-engineering-anatomy-of-a-prompt should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/anatomy-of-a-prompt/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How prompt-engineering-anatomy-of-a-prompt Compares
| Feature / Agent | prompt-engineering-anatomy-of-a-prompt | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Sub-skill of prompt-engineering: Anatomy of a Prompt (+1).
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Anatomy of a Prompt (+1) ## Anatomy of a Prompt ``` [SYSTEM CONTEXT] - Who is the AI, what are its capabilities/constraints [TASK DESCRIPTION] - What needs to be done [INPUT DATA] - The specific content to process [OUTPUT FORMAT] - How the response should be structured [EXAMPLES] - Optional: demonstrations of desired behavior [CONSTRAINTS] - Limitations, things to avoid ``` ## The Prompt Engineering Loop ``` 1. Define Goal -> What do you want to achieve? 2. Draft Prompt -> Initial attempt 3. Test -> Run with diverse inputs 4. Analyze -> Identify failures and patterns 5. Refine -> Improve based on analysis 6. Repeat -> Until quality meets requirements ```
Related Skills
plan-review-prompt-refresh-after-plan-edits
Refresh reviewer prompt files from the latest on-disk plan before every adversarial re-review. Prevents Codex/Gemini from critiquing stale plan text after local edits.
label-driven-prompt-generation-architecture
Pattern for building automation scripts that classify GitHub issues into prompt templates using label-based routing and extract contextual data for batch processing
agent-team-prompt-generation
Create self-contained execution prompts that define multi-role workflows for Codex sessions without external dependencies
live-state-aware-overnight-implementation-prompts
Design overnight implementation prompts that begin with a live repo/CI precheck so workers continue from partial progress instead of replaying stale handoffs.
single-terminal-gh-issue-prompts
Generate live issue-specific Codex prompts for a single terminal, with repo-aware path contracts and plan-gate safety checks.
provider-review-prompt-path-guard
Prevent adversarial review dispatch failures caused by sandbox/tmp path mismatches and provider CLI working-directory drift when launching Codex or Gemini with prompt files.
plan-resubmit-wave-prompts
Run a planning-only multi-terminal wave to harden blocked `status:plan-review` issues for fresh adversarial re-review, with zero implementation work and explicit path ownership.
overnight-parallel-agent-prompts
Design self-contained prompts for 3-5 terminals to run overnight without supervision. Ensures zero git contention, provider-optimal allocation, and a clear morning deliverable summary.
adversarial-review-prompt-refresh-guard
Prevent stale plan/code review prompts from being sent to Codex/Gemini after the underlying artifact changed.
absolute-path-review-prompt-dispatch
Prevent adversarial review dispatch failures caused by relative prompt paths, superseded background sessions, and stale completion notices when launching Codex/Gemini review jobs.
engineering-solver-domain-recon
Deep reconnaissance of an engineering solver domain (OrcaWave, OrcaFlex, CalculiX, OpenFOAM, etc.) across a multi-repo ecosystem — map infrastructure, issues, skills, data artifacts, machine constraints, and solver queue state before planning work.
engineering-domain-reconnaissance
Class-level external engineering domain reconnaissance: field development, external drive ingest planning, and source-to-artifact conversion.