# Forge Plan

> Use when the user asks to plan, break down, sequence, or add tasks in a repo containing `docs/forge/` or governed by FORGE. Shapes bounded tasks (scope, file_scope, dependencies, review needs) in the configured task source without implementing.

- Skill: `redteamlife/forge-plan` (Agent Skill)
- Install (CLI): `npx skillmds@latest add redteamlife/forge-plan`
- Raw SKILL.md: https://api.skillmd.com/api/skills/redteamlife/forge-plan/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: redteamlife (https://skillmd.com/u/redteamlife)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/redteamlife/forge-plan

---


# FORGE Plan

Use this skill when the user asks to plan, break down, sequence, or prepare
FORGE-governed work.

## Workflow

1. Read `docs/forge/CONTEXT.md` if present, then `docs/forge/AI.md` if present.
2. Identify the authoritative task source: local `TASKS.index.yaml` plus task files, legacy `TASKS.yaml`, GitHub Issues, GitLab Issues, or external tracker.
3. Use `../references/lifecycle-map.md` only when lifecycle routing is ambiguous.
4. Shape tasks with bounded scope, file scope, dependencies, contract files,
   and review requirements.
5. For design/architecture work, record a `task_type: design` task whose
   document lives under `docs/forge/designs/`. Design tasks are tracked by
   `review_state` (draft|in-review|changes-requested|accepted) and are exempt
   from execution gates — do not attach a `gates:` block to them.
6. Do not implement unless the user explicitly switches to build or
   `forge-execute-task`.

## Hard Stops

Stop when the authoritative task source is unclear, a task cannot be bounded,
or a contract/architecture decision is needed before sequencing.

## Evidence Required

- task entries, issue links, or explicit human-approved task breakdown