forge-cc 0.1.2 → 0.1.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/skills/forge-go.md +8 -9
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "forge-cc",
3
- "version": "0.1.2",
3
+ "version": "0.1.3",
4
4
  "description": "Pre-PR verification harness for Claude Code agents — gate runner + CLI + MCP server",
5
5
  "type": "module",
6
6
  "license": "MIT",
package/skills/forge-go.md CHANGED
@@ -6,9 +6,11 @@ Execute milestones from your PRD with wave-based agent teams, self-healing verif
6
6
 
7
7
  Follow these steps exactly. The execution engine at `src/go/executor.ts` provides the programmatic logic — this skill drives the agent orchestration.
8
8
 
9
- ### Step 1 — Orient
9
+ ### Step 1 — Orient + Choose Mode
10
10
 
11
- Read project state files to determine current position:
11
+ **This step has two parts. Complete BOTH before moving to Step 2. Do NOT read any other files, do NOT start pre-flight checks, do NOT read the PRD until both parts are done.**
12
+
13
+ **Part A — Read state (only these 3 files, nothing else):**
12
14
 
13
15
  ```
14
16
  Read these files in parallel:
@@ -32,15 +34,12 @@ If all milestones are complete:
32
34
 
33
35
  > All milestones complete! Create a PR with `gh pr create` or run `/forge:spec` to start a new project.
34
36
 
35
- ### Step 1.5 — Choose Execution Mode (MANDATORY)
36
-
37
- **STOP. Do NOT proceed to Step 2 until this step is complete.**
37
+ **Part B — Ask execution mode (MANDATORY — do this IMMEDIATELY after Part A):**
38
38
 
39
- If `--auto` was passed as an argument, set mode to auto and skip the prompt below.
39
+ If `--auto` was passed as an argument, set mode to auto and skip the prompt.
40
40
 
41
- Otherwise, you MUST use the AskUserQuestion tool RIGHT NOW to ask the user which mode they want. Do not skip this. Do not assume single milestone. Do not proceed without an answer.
41
+ Otherwise: **your very next tool call MUST be AskUserQuestion.** No file reads, no git commands, no exploration — ask the user first. Use exactly these parameters:
42
42
 
43
- Use AskUserQuestion with exactly these parameters:
44
43
  - question: "How should this project be executed?"
45
44
  - header: "Mode"
46
45
  - options:
@@ -48,7 +47,7 @@ Use AskUserQuestion with exactly these parameters:
48
47
  - label: "Auto (all milestones)", description: "Chain all remaining milestones with fresh context between each. After each milestone, prints a continuation prompt for the next session."
49
48
  - multiSelect: false
50
49
 
51
- **Wait for the user's response before continuing.** Store their choice and apply it in Step 8 (Route Next).
50
+ **Wait for the user's response before continuing.** Do not proceed to Step 2 until you have their answer. Store the choice for Step 8 (Route Next).
52
51
 
53
52
  ### Step 2 — Pre-flight Checks
54
53