agentleFS
V-SongbirdV-Songbird/foreman/skills/craft-prompt/SKILL.md

craft-prompt

Skill35 starsChanged 52 days agoMITView on GitHub

Advanced surface, separate from Foreman's core roadmap job — a standalone prompt builder for work that has no roadmap entry behind it. Use on an explicit prompt-crafting request. Builds or refines a self-contained prompt for a fresh session following Foreman's template: asks which optional sections to include, gathers the missing intent, grounds paths and checks, assembles the XML, then runs it here as one or several tracked tasks, hands it to a background agent, or copies it to the clipboard.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. mrdainami/omni-video-director★ 16same name
    2. sungjunlee/craftkit★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository4 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 1 is distinctive, and 8 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 8

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write for a destination with no memory of this conversation — every field must be filled so it can act cold.

    line 18
  2. Very specific:

    Ask each call's questions together — AskUserQuestion in Claude Code.

    line 21
  3. Very specific:

    Read call-1.md (${CLAUDE_PLUGIN_ROOT}/skills/craft-prompt/call-1.md) and follow it.

    line 37
  4. Very specific:

    Read ground-files.md (${CLAUDE_PLUGIN_ROOT}/skills/craft-prompt/ground-files.md) and follow it.

    line 43
  5. Very specific:

    When Call 1 Q2 selected any optional section, or Call 1 Q4 answered Yes, read call-4.md …

    line 63
  6. Very specific:

    When any answer comes back as a don't-know, or Call 2 Q3 comes back as I can only name the area or names no file, read dont-know.md …

    line 70
  7. Very specific:

    Read resolve-files.md (${CLAUDE_PLUGIN_ROOT}/skills/craft-prompt/resolve-files.md) and follow it.

    line 77
  8. Very specific:

    Read assemble.md (${CLAUDE_PLUGIN_ROOT}/skills/craft-prompt/assemble.md) and follow it.

    line 96
  9. Very specific:

    Read deliver.md (${CLAUDE_PLUGIN_ROOT}/skills/craft-prompt/deliver.md) and follow it.

    line 102

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

foreman:craft-prompt — interactive prompt builder

Foreman runs in Claude Code, Codex and Antigravity. Every step applies to every host unless it names one. Read the shared runtime first: it covers plugin paths, JSON payloads, questions and authorization for every host.

Advanced tool, separate from Foreman's core job. An ordinary implementation request does not call for a prompt-crafting interview: it goes through the foreman entrance, which builds its own handoff out of the roadmap entry. This skill is for the case with no roadmap entry behind it: a standalone prompt, asked for explicitly. Write for a destination with no memory of this conversation — every field must be filled so it can act cold.

Ask each call's questions together — AskUserQuestion in Claude Code; in Codex, the picker in questions.md, within its limits. With no usable question tool, ask one self-contained plain-text question. Ask directly: never say Foreman requires the question or cite a skill as the reason. Text supplied with the request (in Claude Code, the skill's args) seeds the task description; skip a question only when the user's own words already answer it.

Each step below lives in its own file beside this one. Read it when the interview reaches that step and follow it; a step this file skips is never read.


Call 1 — task type, optional sections, starting point, and flavor

Read call-1.md (${CLAUDE_PLUGIN_ROOT}/skills/craft-prompt/call-1.md) and follow it.


Ground the file options (one read-only pass, before Call 2)

Read ground-files.md (${CLAUDE_PLUGIN_ROOT}/skills/craft-prompt/ground-files.md) and follow it.


Call 2 — required fields (batch all 4)

Read call-2.md (${CLAUDE_PLUGIN_ROOT}/skills/craft-prompt/call-2.md) and follow it.


Call 3 — verification (conditional)

Skip this call only if the task type is pure research/investigation with no code changes.

Otherwise read call-3.md (${CLAUDE_PLUGIN_ROOT}/skills/craft-prompt/call-3.md) and follow it.


Call 4-N — optional section details

When Call 1 Q2 selected any optional section, or Call 1 Q4 answered Yes, read call-4.md (${CLAUDE_PLUGIN_ROOT}/skills/craft-prompt/call-4.md) and follow it.


When an answer is "I don't know"

When any answer comes back as a don't-know, or Call 2 Q3 comes back as I can only name the area or names no file, read dont-know.md (${CLAUDE_PLUGIN_ROOT}/skills/craft-prompt/dont-know.md) and follow it.


Resolve the named files (craft-time, once)

Read resolve-files.md (${CLAUDE_PLUGIN_ROOT}/skills/craft-prompt/resolve-files.md) and follow it.


Call 5 — how to run it

Honor a destination the user already stated. Otherwise read destination-question.md (${CLAUDE_PLUGIN_ROOT}/skills/roadmap/destination-question.md) now and do exactly what it says. Call 3 already gathered the verification, so the count is known here — it never removes an option, it decides which one carries a caution. Foreman never asks which model runs the work and never sets one: a background agent inherits this session's model, and a pasted prompt runs wherever the user pastes it.


Assemble the handoff — one call to craft-handoff.js

Read assemble.md (${CLAUDE_PLUGIN_ROOT}/skills/craft-prompt/assemble.md) and follow it.


Deliver

Read deliver.md (${CLAUDE_PLUGIN_ROOT}/skills/craft-prompt/deliver.md) and follow it.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.