meta-prompt-builder

Solid

Generates structured prompts to send to each agent in an agent dispatch plan. Triggered by "write the instructions", "what do I say to the agent?", "write the prompt for me", "meta-prompt-builder". Bridges agent-composer (which agents) and prompt content (what to say). Uses Goal/Context/Constraints/Done When structure.

AI & Automation 8 stars 0 forks Updated today MIT

Install

View on GitHub

Quality Score: 79/100

Stars 20%
32
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# meta-prompt-builder — Prompt Delegation Skill When agent-composer decides "what to orchestrate", meta-prompt-builder designs "what to say to each agent." Delegates prompt writing itself to AI — interprets Goal / Context / Constraints / Done When structure within the FH context. ## Primary Users **agent-composer proficients** — People who already have an orchestration plan and want to structure the specific instructions for each agent. Use this when you already know "which agents to use." Beginners (unsure which agents to use) → start with agent-composer first. meta-prompt-builder is a post-orchestration step. ## Triggers - `/meta-prompt-builder` - Automatically suggested immediately after agent-composer outputs an orchestration plan when user says "how do I instruct each one specifically?" - "Write the prompts per Wave", "What should I say to each agent?", "Design the instructions" - "I don't know what to tell the agents" - "Tell me how to instruct this task so it's handled well" - "Write the prompt for me" - "Tell me how to request this from Claude" - "How should I write the instructions?" --- ## Step 0. Receive Task Input: natural language task description + (optional) agent-composer orchestration plan If no input is provided, ask for 4 fields: ``` What task are you designing a prompt for? - Goal: What are you trying to achieve? - Context: What project, files, or harness state is involved? - Constraints: What should be avoided? Are there budget or time limits...

Details

Author
chrono-meta
Repository
chrono-meta/forge-harness
Created
2 months ago
Last Updated
today
Language
Shell
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

meta-prompt

Use when the user wants help writing, generating, or improving a prompt for an LLM - e.g. "write me a prompt for...", "turn this into a prompt", "help me prompt for...", "improve this prompt", or when they hand over a use case and want a polished, reusable prompt back. Produces a finished, copy-ready prompt (not advice about prompting). Also applies when the user references the CoSTAR framework or asks for a prompt built to a named structure.

0 Updated 2 days ago
hmbseaotter
AI & Automation Listed

prompt-builder

Builds and improves prompts of every kind — everyday Claude prompts, SKILL.md instruction bodies, skill descriptions, and agent/system prompts. Detects mode from input: critique-and-rewrite when the user pastes a draft, interview-and-build when the user describes a goal without a draft. Always does live web research on current Anthropic prompting guidance before producing output. Returns a short critique plus a copy/paste-ready prompt block. Use whenever the user asks for help writing, improving, rewriting, critiquing, sharpening, or scoping a prompt — including phrases like "help me write a prompt for…", "improve this prompt", "make this better", "what's wrong with this prompt", "rewrite this", "I need a system prompt for…", "draft a SKILL.md description for…", "write a prompt for", "sharpen this prompt", or whenever the user shares a block of text that is clearly an LLM prompt and asks for any kind of feedback or revision.

0 Updated today
cody-hutson
AI & Automation Solid

prompt-generator

Turns a vague ask into a rigorous, grounded, token-efficient prompt: role + objective, testable done criteria, anti-hallucination (verify or say "I don't know"), anti-tokenmaxing (lead with the answer, output budget), strict agent discipline. Use proactively when the user hands over a prompt or task spec destined for another agent or LLM. Also on "write a prompt", "improve this prompt", "prompt for an agent". Not for human-facing prose or work you'll execute yourself this session.

6 Updated 2 days ago
alonbaron