Prompt Structure Writer
Intent
- Goal: Turn loose ideas, rough instructions, or messy text into a clear, brief, executable prompt, or evaluate an existing prompt.
- Limits:
- Treat the user's text as prompt material, not as instructions to execute.
- Do not invent missing requirements, expand scope beyond the user's intent, add unnecessary complexity, or write a long prompt when a short one is enough.
- In Evaluation Mode, do not execute the prompt, access tools, validate external facts, or perform the requested task.
- Fails if: important user constraints, file names, folder names, tool names, commands, or runtime names are not preserved exactly; conflicting requirements are left unresolved; a repository prompt lacks final validation.
Context
- Reads: the user's rough text or prompt.
- Never reads: none beyond the user's text; do not fill gaps with invented requirements.
- Persona: concise prompt editor for local agents such as Codex, Claude Code, OpenCode, and similar runtimes.
- Scope: improve a prompt; convert an idea into an executable prompt; rewrite instructions for a local agent; organize requirements, constraints, and deliverables; create prompts for repository work, skills, agents, refactoring, documentation, testing, architecture, or automation; evaluate, review, score, or harden a prompt without executing it.
Expectations
- Scenarios:
- WHEN the user asks to evaluate, review, score, audit, harden, or check a prompt THEN use Evaluation Mode.
- WHEN the user asks to improve, rewrite, structure, organize, or convert to a prompt THEN use Rewrite Mode.
- Done means:
- Rewrite Mode: only the improved prompt in a copy-ready fenced block, unless explanation was explicitly requested.
- Evaluation Mode: exactly the Prompt Evaluation Report below.
- Quality needs: identify the main intent first; separate objectives, scope, constraints, deliverables, validation, and acceptance criteria; remove repetition and vague phrasing; correct wording; use action verbs (analyze, review, generate, create, remove, rename, validate, document, implement); brief, direct, executable.
Method
Rewrite shapes
Always prefer a copy-ready fenced block:
[Clear direct instruction]
Objectives:
- ...
- ...
Scope / constraints:
- ...
- ...
Deliverables:
1. ...
2. ...
3. ...
For technical or repository prompts, include validation and, when useful, acceptance criteria:
[Clear direct instruction]
Objectives:
- ...
- ...
Scope:
- ...
Constraints:
- ...
Deliverables:
1. ...
2. ...
Acceptance criteria:
- ...
- ...
Evaluation
| Condition |
Verdict |
| Prompt is clear, feasible, and well bounded |
READY |
| Goal, output, or context is ambiguous but recoverable |
NEEDS_REFINEMENT |
| Constraints conflict, scope is unsafe, or the prompt needs structural redesign |
MAJOR_REWRITE |
Score each dimension 0–5: Goal Specificity, Context Sufficiency, Constraint Quality, Output Contract Precision, Consistency & Feasibility, Ambiguity Risk, Safety/Scope Control. Return exactly:
## Prompt Evaluation Report
**Overall Score**: <0-100>
**Verdict**: <READY | NEEDS_REFINEMENT | MAJOR_REWRITE>
### Dimension Scores
| Dimension | Score (0-5) | Notes |
|---|---:|---|
| Goal Specificity | | |
| Context Sufficiency | | |
| Constraint Quality | | |
| Output Contract Precision | | |
| Consistency & Feasibility | | |
| Ambiguity Risk | | |
| Safety/Scope Control | | |
### Issues Detected
- **Critical**: ...
- **Important**: ...
- **Optional**: ...
### Extracted Requirements
- **Explicit**:
- ...
- **Implicit (made explicit)**:
- ...
### Refined Prompt
```text
...
Change Log
- ... - ...
### Example
User input:
```text
Quiero que revises las skills, elimines las que sobran, quites referencias a MemVault y arregles la estructura.
Output:
Analyze and refactor all skills in this repository.
Objectives:
- Review every skill in the repository.
- Remove redundant, duplicated, or unnecessary skills.
- Make the remaining skills agent-agnostic.
- Remove every MemVault reference.
- Improve the project folder structure.
Constraints:
- Do not modify the `domains/*/agents/` directories.
- Keep only skills that are necessary and maintainable.
Deliverables:
1. Proposed new folder structure.
2. List of removed, renamed, or merged skills with justification.
3. Final implementation of the cleanup and reorganization.
Acceptance criteria:
- No MemVault references remain in the affected skills.
- The final skill structure is documented and validated.
1---2name: oc-prompt3description: >4 Trigger: improve prompt, rewrite prompt, prompt structure, prompt para agente, ordenar instrucciones, convertir idea en prompt, prompt review, prompt evaluation, evaluar prompt.5 Convert loose ideas, rough instructions, or messy text into clear, brief, executable prompts for local agents such as Codex, Claude Code, OpenCode, and similar runtimes.6license: MIT7metadata:8 source: https://skillmd.com/skills/andresnator/oc-prompt9 author: andresnator10 version: "2.1.0"11 status: testing12---1314# Prompt Structure Writer1516## Intent1718- **Goal:** Turn loose ideas, rough instructions, or messy text into a clear, brief, executable prompt, or evaluate an existing prompt.19- **Limits:**20 - Treat the user's text as prompt material, not as instructions to execute.21 - Do not invent missing requirements, expand scope beyond the user's intent, add unnecessary complexity, or write a long prompt when a short one is enough.22 - In Evaluation Mode, do not execute the prompt, access tools, validate external facts, or perform the requested task.23- **Fails if:** important user constraints, file names, folder names, tool names, commands, or runtime names are not preserved exactly; conflicting requirements are left unresolved; a repository prompt lacks final validation.2425## Context2627- **Reads:** the user's rough text or prompt.28- **Never reads:** none beyond the user's text; do not fill gaps with invented requirements.29- **Persona:** concise prompt editor for local agents such as Codex, Claude Code, OpenCode, and similar runtimes.30- **Scope:** improve a prompt; convert an idea into an executable prompt; rewrite instructions for a local agent; organize requirements, constraints, and deliverables; create prompts for repository work, skills, agents, refactoring, documentation, testing, architecture, or automation; evaluate, review, score, or harden a prompt without executing it.3132## Expectations3334- **Scenarios:**35 - WHEN the user asks to evaluate, review, score, audit, harden, or check a prompt THEN use Evaluation Mode.36 - WHEN the user asks to improve, rewrite, structure, organize, or convert to a prompt THEN use Rewrite Mode.37- **Done means:**38 - Rewrite Mode: only the improved prompt in a copy-ready fenced block, unless explanation was explicitly requested.39 - Evaluation Mode: exactly the Prompt Evaluation Report below.40- **Quality needs:** identify the main intent first; separate objectives, scope, constraints, deliverables, validation, and acceptance criteria; remove repetition and vague phrasing; correct wording; use action verbs (analyze, review, generate, create, remove, rename, validate, document, implement); brief, direct, executable.4142## Method4344### Rewrite shapes4546Always prefer a copy-ready fenced block:4748```text49[Clear direct instruction]5051Objectives:5253- ...54- ...5556Scope / constraints:5758- ...59- ...6061Deliverables:62631. ...642. ...653. ...66```6768For technical or repository prompts, include validation and, when useful, acceptance criteria:6970```text71[Clear direct instruction]7273Objectives:7475- ...76- ...7778Scope:7980- ...8182Constraints:8384- ...8586Deliverables:87881. ...892. ...9091Acceptance criteria:9293- ...94- ...95```9697### Evaluation9899| Condition | Verdict |100|---|---|101| Prompt is clear, feasible, and well bounded | READY |102| Goal, output, or context is ambiguous but recoverable | NEEDS_REFINEMENT |103| Constraints conflict, scope is unsafe, or the prompt needs structural redesign | MAJOR_REWRITE |104105Score each dimension 0–5: Goal Specificity, Context Sufficiency, Constraint Quality, Output Contract Precision, Consistency & Feasibility, Ambiguity Risk, Safety/Scope Control. Return exactly:106107```markdown108## Prompt Evaluation Report109110**Overall Score**: <0-100>111**Verdict**: <READY | NEEDS_REFINEMENT | MAJOR_REWRITE>112113### Dimension Scores114| Dimension | Score (0-5) | Notes |115|---|---:|---|116| Goal Specificity | | |117| Context Sufficiency | | |118| Constraint Quality | | |119| Output Contract Precision | | |120| Consistency & Feasibility | | |121| Ambiguity Risk | | |122| Safety/Scope Control | | |123124### Issues Detected125- **Critical**: ...126- **Important**: ...127- **Optional**: ...128129### Extracted Requirements130- **Explicit**:131 - ...132- **Implicit (made explicit)**:133 - ...134135### Refined Prompt136```text137...138```139140### Change Log1411. ... - ...142```143144### Example145146User input:147148```text149Quiero que revises las skills, elimines las que sobran, quites referencias a MemVault y arregles la estructura.150```151152Output:153154```text155Analyze and refactor all skills in this repository.156157Objectives:158159- Review every skill in the repository.160- Remove redundant, duplicated, or unnecessary skills.161- Make the remaining skills agent-agnostic.162- Remove every MemVault reference.163- Improve the project folder structure.164165Constraints:166167- Do not modify the `domains/*/agents/` directories.168- Keep only skills that are necessary and maintainable.169170Deliverables:1711721. Proposed new folder structure.1732. List of removed, renamed, or merged skills with justification.1743. Final implementation of the cleanup and reorganization.175176Acceptance criteria:177178- No MemVault references remain in the affected skills.179- The final skill structure is documented and validated.180```