Skill

start

Initiate a new Forge workflow. Creates .forge/ state and begins the discovery phase. User-invoked only: do not auto-trigger.

npx claudepluginhub caseyrtalbot/forge --plugin forge

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Initiate a new Forge workflow. Check for existing workflow state in `.forge/`, create a new workflow if none exists, and hand off to `discover-intent` to begin collaborative refinement of what to build. User-invoked only: do not auto-trigger this skill.

SKILL.md

Similar Skills

finishing-a-development-branch

174.6k

Verifies tests pass on completed feature branch, presents options to merge locally, create GitHub PR, keep as-is or discard; executes choice and cleans up worktree.

superpowers

systematic-debugging

174.6k

Guides root cause investigation for bugs, test failures, unexpected behavior, performance issues, and build failures before proposing fixes.

10 files

superpowers

writing-plans

174.6k

Writes implementation plans from specs for multi-step tasks, mapping files and breaking into TDD bite-sized steps before coding.

1 file

superpowers

Stats

Stars0

Forks0

Last CommitApr 11, 2026

Actions

View Source View Plugin View on GitHub View README

Start

Initiate a new Forge workflow. Check for existing workflow state in .forge/, create a new workflow if none exists, and hand off to discover-intent to begin collaborative refinement of what to build. User-invoked only: do not auto-trigger this skill.

Usage

/forge:start [description]

The optional [description] is a short phrase describing what the user wants to build. It becomes the initial intent field in forge-state.json and seeds the first discover-intent question.

If an active workflow exists, ask the user whether to resume or archive the existing one. Never decide unilaterally.

Process

Check .forge/forge-state.json for existing workflow state.

If an active workflow exists, show its current phase and progress, then ask the user whether to resume or archive.

If no workflow or user chose archive, create .forge/ directory and write a fresh forge-state.json using the initialization template (phase: discovery, completed_phases: [], created_at: <now>).

Record the user's [description] argument (if provided) as the initial intent.

Invoke the discover-intent skill to begin Phase 1.

Evidence

.forge/forge-state.json exists with phase: discovery after this skill runs.

discover-intent is the next active skill.

Transitions

→ discover-intent: Workflow state is initialized. Hand off to discovery phase.

Start

Usage

/forge:start [description]

The optional [description] is a short phrase describing what the user wants to build. It becomes the initial intent field in forge-state.json and seeds the first discover-intent question.

Never create or overwrite `.forge/forge-state.json` if an active workflow already exists. An "active workflow" means `completed_phases` does not include all six phases. Overwriting active state destroys accumulated evidence and phase history.

If an active workflow exists, ask the user whether to resume or archive the existing one. Never decide unilaterally.

Process

Check .forge/forge-state.json for existing workflow state.
If an active workflow exists, show its current phase and progress, then ask the user whether to resume or archive.
If no workflow or user chose archive, create .forge/ directory and write a fresh forge-state.json using the initialization template (phase: discovery, completed_phases: [], created_at: <now>).
Record the user's [description] argument (if provided) as the initial intent.
Invoke the discover-intent skill to begin Phase 1.

Evidence

.forge/forge-state.json exists with phase: discovery after this skill runs.
discover-intent is the next active skill.

Transitions

→ discover-intent: Workflow state is initialized. Hand off to discovery phase.