foreman-plan
Headless implementation-plan authoring for the Foreman planning stage. Explore the target repo first, then write a deep, decomposition-aware plan that the grill→ADR/PRD→issues pipeline can build on — goals, seams, data/interface changes, risks, sequencing, and testing strategy. No placeholders. Writes the plan body and stops.
npx skills add VisionForge-OU/foreman --skill foreman-plan --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# foreman-plan (Adapted from obra/superpowers `writing-plans` (MIT) — see NOTICE. Re-aimed at Foreman's planning stage: this plan is the **input to the grill stage**, which turns it into an ADR + PRD, which `foreman-to-issues` then slices — so it stays at the design/seam level and does NOT emit the per-step TDD checklist that `foreman-to-issues` and `foreman-tdd` own. Removed the interactive execution-handoff prompts; there is no live human in this run.) You are the planner, running **headless**. Write a deep implementation plan for the feature request, grounded in *this* repository. Produce the plan body as markdown at the exact path Foreman gives you (body only — no YAML frontmatter) and stop. Do not ask questions; anything you genuinely cannot resolve is recorded as an explicit assumption or open risk for the grill stage to challenge. ## 1. Explore before you plan Assume the reader is a skilled engineer who knows almost nothing about this codebase. Before proposing anything, learn the ground truth: - **Domain language:** read `CONTEXT.md` / `CONTEXT-MAP.md` if present and use the project's canonical terms throughout. - **Prior decisions:** read `docs/adr/`. Respect accepted ADRs
- 1. Explore before you plan
- 2. Map the file structure first
- 3. Write the plan
- 4. No placeholders
- 5. Self-review before you stop
What does the foreman-plan skill do?
Headless implementation-plan authoring for the Foreman planning stage. Explore the target repo first, then write a deep, decomposition-aware plan that the grill→ADR/PRD→issues pipeline can build on — goals, seams, data/interface changes, risks, sequencing, and testing strategy. No placeholders. Writes the plan body and stops.
How do I install it?
Run `npx skills add VisionForge-OU/foreman --skill foreman-plan --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From VisionForge-OU/foreman, a repository with 421 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.