5-phase-workflow 3.1.1 → 3.1.2

package/README.md

@@ -25,7 +25,6 @@ Then configure the project once:
 
 ```bash
 /5:configure
-/5:implement CONFIGURE
 ```
 
 This adds the foifi rules to `AGENTS.md` as one marked block, links your existing standards from it, and makes `CLAUDE.md` include it. Nothing else in your files or settings changes.

package/docs/workflow-guide.md

@@ -90,10 +90,9 @@ First-time setup:
 
 ```text
 /5:configure
-/5:implement CONFIGURE
 ```
 
-`/5:configure` writes `.5/config.json`, sets `plansDirectory` to `.5/planning` in `.claude/settings.json`, and writes the CONFIGURE plan. `/5:implement CONFIGURE` adds the workflow rules to AGENTS.md as one marked block that links the repository's own standards, appends `@AGENTS.md` to CLAUDE.md when it lacks that line, and generates scoped rules. Nothing outside the block changes.
+`/5:configure` writes `.5/config.json`, sets `plansDirectory` to `.5/planning` in `.claude/settings.json`, writes the CONFIGURE plan, and then runs `/5:implement CONFIGURE` itself, which adds the workflow rules to AGENTS.md as one marked block that links the repository's own standards, appends `@AGENTS.md` to CLAUDE.md when it lacks that line, and generates scoped rules. Nothing outside the block changes.
 
 Refresh the AGENTS.md block and the rules later with:
 
@@ -135,5 +134,5 @@ v2.0.0 removes old commands during upgrade:
 | `/5:review` | Review changes for correctness and standards |
 | `/5:address-review-findings` | Fix clear findings, ask about real decisions |
 | `/5:analyze-feature` | Document a feature with mermaid diagrams |
-| `/5:configure` | Create project config and CONFIGURE plan |
+| `/5:configure` | Create project config and CONFIGURE plan, then implement it |
 | `/5:reconfigure` | Refresh the AGENTS.md block and rules |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "5-phase-workflow",
-  "version": "3.1.1",
+  "version": "3.1.2",
   "description": "A dev-workflow for Claude Code and Codex",
   "bin": {
     "foifi": "bin/install.js"

package/src/commands/5/configure.md

@@ -1,15 +1,15 @@
 ---
 name: 5:configure
-description: Configures the project. Analyzes project, gathers preferences, writes config.json, points Claude Code plan mode at .5/planning/, and creates .5/planning/CONFIGURE.md. Follow up with /5:implement CONFIGURE.
-allowed-tools: Read, Write, Bash, Glob, Grep, AskUserQuestion
+description: Configures the project. Analyzes project, gathers preferences, writes config.json, points Claude Code plan mode at .5/planning/, creates .5/planning/CONFIGURE.md, then runs /5:implement CONFIGURE itself.
+allowed-tools: Agent, Read, Write, Edit, Glob, Grep, Bash, Workflow, Skill, AskUserQuestion
 user-invocable: true
 ---
 
 <role>
 You are a Project Configurator. You analyze a project, gather preferences, and write config.json plus a unified plan.
-You do NOT write AGENTS.md, CLAUDE.md, or rules directly — those are /5:implement's job.
+You do NOT write AGENTS.md, CLAUDE.md, or rules directly — those are /5:implement's job, and you start it yourself once the plan is written.
 You write ONLY to: .5/config.json, .5/version.json, .5/planning/CONFIGURE.md, .gitignore, and the `plansDirectory` key of .claude/settings.json (Claude Code only).
-After writing config.json and the unified plan, you are DONE. Exit immediately.
+After writing config.json and the unified plan, you hand off to `/5:implement CONFIGURE`.
 </role>
 
 # Configure (Project Setup Plan)
@@ -18,16 +18,11 @@ Current commit: !`git rev-parse --short HEAD 2>/dev/null || echo "none"`
 
 ## Overview
 
-This command prepares project configuration. It analyzes the project, asks preference questions, writes `.5/config.json`, points Claude Code plan mode at `.5/planning/`, and writes a plan at `.5/planning/CONFIGURE.md`.
-
-After running this command, proceed through the standard phases:
-1. **`/5:configure`** (this command) - Create config and CONFIGURE plan
-2. `/5:implement CONFIGURE` - Execute configuration (uses `configure-agents-md` and `configure-rules`)
-3. `/5:review` - Review generated files if desired
+This command prepares project configuration. It analyzes the project, asks preference questions, writes `.5/config.json`, points Claude Code plan mode at `.5/planning/`, writes a plan at `.5/planning/CONFIGURE.md`, and then runs `/5:implement CONFIGURE` itself, which executes the plan with `configure-agents-md` and `configure-rules` and reviews the result. The user runs only this one command.
 
 ## ⚠️ CRITICAL SCOPE CONSTRAINT
 
-**THIS COMMAND WRITES config.json AND CREATES THE CONFIGURE PLAN. NOTHING ELSE.**
+**THIS COMMAND WRITES config.json AND CREATES THE CONFIGURE PLAN, THEN HANDS OFF TO `/5:implement CONFIGURE`. NOTHING ELSE.**
 
 Your job in this command:
 ✅ Analyze project (detect type, build commands, etc.)
@@ -35,7 +30,7 @@ Your job in this command:
 ✅ Write `.5/config.json` directly
 ✅ Set `plansDirectory` in `.claude/settings.json` (Claude Code only)
 ✅ Create the plan at `.5/planning/CONFIGURE.md` for remaining work
-✅ Tell user to run /5:implement CONFIGURE
+✅ Run `/5:implement CONFIGURE` right after the plan is written
 
 Your job is NOT:
 ❌ Write AGENTS.md or CLAUDE.md directly (/5:implement does this)
@@ -43,9 +38,9 @@ Your job is NOT:
 ❌ Skip user interaction
 ❌ Assume project structure
 
-**After writing config.json, creating the unified plan, and informing the user, YOUR JOB IS COMPLETE. EXIT IMMEDIATELY.**
+**After writing config.json and the unified plan, run `/5:implement CONFIGURE`. The rest is its job.**
 
-**If you find yourself writing AGENTS.md, CLAUDE.md, or rules, STOP IMMEDIATELY. You should only be writing config.json, the settings key, and the plan.**
+**If you find yourself writing AGENTS.md, CLAUDE.md, or rules before `/5:implement CONFIGURE` runs, STOP IMMEDIATELY. You should only be writing config.json, the settings key, and the plan.**
 
 ## Configuration Process
 
@@ -173,6 +168,7 @@ Context7 provides up-to-date, version-specific documentation and code examples d
 - "Generate `.claude/rules/` files? These are scoped instruction files that automatically load when the agent works with matching file types (e.g., testing rules load only when editing test files, code-style rules load only for source files)."
   - Options: "Yes (recommended)", "Skip"
 - Note: Rules complement AGENTS.md — they provide focused, file-type-scoped directives derived from your project's actual conventions.
+- On Codex, the rules live in the foifi block of `AGENTS.md`. When the user skipped AGENTS.md in step 2j, do not ask: set `rules.generate` to `false`.
 
 **2l. Git-ignore workflow folders:**
 - "`.5/planning/` will hold your plans. `.5/features/` will hold implementation state and review findings. Which should git ignore?"
@@ -227,7 +223,9 @@ Ensure `.5/.reconfig-reminder` is gitignored (it's a transient runtime flag that
 
 ### Step 3: Create Configuration Plan
 
-Write `.5/planning/CONFIGURE.md` containing all gathered data:
+If the user skipped both AGENTS.md (step 2j) and rules (step 2j2), there is nothing to implement: delete `.5/planning/CONFIGURE.md` if an earlier run left it, so no later `/5:implement` applies what the user just declined. Then skip Steps 3 and 4, tell the user "Configuration saved to `.5/config.json`", and stop.
+
+Otherwise write `.5/planning/CONFIGURE.md` containing all gathered data. When the user skipped AGENTS.md in step 2j, leave out everything about AGENTS.md and CLAUDE.md: the `configure agents md` component, Requirement 1, its acceptance criteria and Module Impact row, and the "After configure agents md" ordering. The plan then generates only the rules, and nothing touches `AGENTS.md` or `CLAUDE.md`. The template below shows the plan with both selected:
 
 ```markdown
 ---
@@ -324,21 +322,16 @@ Only generate rules for patterns that were actually detected:
 
 ## Next Steps
 
-1. Run `/5:implement CONFIGURE`.
+1. `/5:configure` runs `/5:implement CONFIGURE` right away; rerun it by hand only if that run was interrupted.
 ```
 
 **Important:** Use `mkdir -p .5/planning` before writing the plan.
 
-### Step 4: Guide User to Next Phase
+### Step 4: Run the Plan
 
-Tell the user:
+Tell the user in one line: "Configuration saved to `.5/config.json`, plan written to `.5/planning/CONFIGURE.md` — implementing it now."
 
-1. "Configuration saved to `.5/config.json`"
-2. "Configuration plan written to `.5/planning/CONFIGURE.md`"
-3. "Next steps:"
-   - "Run `/clear` to reset context"
-   - "Then run `/5:implement CONFIGURE`"
-4. "After that: Run `/5:review` if you want a review of generated files"
+Then run `/5:implement CONFIGURE` right away, without asking: the user already chose what to generate in Step 2. It writes the AGENTS.md block and the rules, verifies them, and runs `/5:review` on the result.
 
 ## Related Documentation
 - [configure-agents-md skill](../../skills/configure-agents-md/SKILL.md)