5-phase-workflow 1.4.0 → 1.4.1

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.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "5-phase-workflow",
3
- "version": "1.4.0",
3
+ "version": "1.4.1",
4
4
  "description": "A 5-phase feature development workflow for Claude Code",
5
5
  "bin": {
6
6
  "5-phase-workflow": "bin/install.js"
@@ -10,7 +10,11 @@ user-invocable: true
10
10
 
11
11
  ## Prerequisites Check
12
12
 
13
- **CRITICAL: Check for configuration before proceeding**
13
+ **CRITICAL: Check for configuration before proceeding (skip for CONFIGURE feature)**
14
+
15
+ If the feature argument is `CONFIGURE`, skip this check entirely — the CONFIGURE workflow is what creates the config file.
16
+
17
+ For all other features, run this check:
14
18
 
15
19
  ```bash
16
20
  if [ ! -f ".claude/.5/config.json" ]; then
@@ -27,7 +31,7 @@ if [ ! -f ".claude/.5/config.json" ]; then
27
31
  fi
28
32
  ```
29
33
 
30
- **If config doesn't exist, STOP IMMEDIATELY. Do not proceed with the workflow.**
34
+ **If config doesn't exist and the feature is NOT `CONFIGURE`, STOP IMMEDIATELY. Do not proceed with the workflow.**
31
35
 
32
36
  Execute an implementation plan by delegating work to agents.
33
37
 
@@ -10,7 +10,11 @@ user-invocable: true
10
10
 
11
11
  ## Prerequisites Check
12
12
 
13
- **CRITICAL: Check for configuration before proceeding**
13
+ **CRITICAL: Check for configuration before proceeding (skip for CONFIGURE feature)**
14
+
15
+ If the feature argument is `CONFIGURE`, skip this check entirely — the CONFIGURE workflow is what creates the config file.
16
+
17
+ For all other features, run this check:
14
18
 
15
19
  ```bash
16
20
  if [ ! -f ".claude/.5/config.json" ]; then
@@ -27,7 +31,7 @@ if [ ! -f ".claude/.5/config.json" ]; then
27
31
  fi
28
32
  ```
29
33
 
30
- **If config doesn't exist, STOP IMMEDIATELY. Do not proceed with the workflow.**
34
+ **If config doesn't exist and the feature is NOT `CONFIGURE`, STOP IMMEDIATELY. Do not proceed with the workflow.**
31
35
 
32
36
  Create an implementation plan that maps a feature spec to concrete components.
33
37
 
@@ -11,7 +11,11 @@ user-invocable: true
11
11
 
12
12
  ## Prerequisites Check
13
13
 
14
- **CRITICAL: Check for configuration before proceeding**
14
+ **CRITICAL: Check for configuration before proceeding (skip for CONFIGURE feature)**
15
+
16
+ If the feature argument is `CONFIGURE`, skip this check entirely — the CONFIGURE workflow is what creates the config file.
17
+
18
+ For all other features, run this check:
15
19
 
16
20
  ```bash
17
21
  if [ ! -f ".claude/.5/config.json" ]; then
@@ -28,7 +32,7 @@ if [ ! -f ".claude/.5/config.json" ]; then
28
32
  fi
29
33
  ```
30
34
 
31
- **If config doesn't exist, STOP IMMEDIATELY. Do not proceed with the workflow.**
35
+ **If config doesn't exist and the feature is NOT `CONFIGURE`, STOP IMMEDIATELY. Do not proceed with the workflow.**
32
36
 
33
37
  ## Overview
34
38
 
@@ -10,7 +10,11 @@ user-invocable: true
10
10
 
11
11
  ## Prerequisites Check
12
12
 
13
- **CRITICAL: Check for configuration before proceeding**
13
+ **CRITICAL: Check for configuration before proceeding (skip for CONFIGURE feature)**
14
+
15
+ If the feature argument is `CONFIGURE`, skip this check entirely — the CONFIGURE workflow is what creates the config file.
16
+
17
+ For all other features, run this check:
14
18
 
15
19
  ```bash
16
20
  if [ ! -f ".claude/.5/config.json" ]; then
@@ -27,7 +31,7 @@ if [ ! -f ".claude/.5/config.json" ]; then
27
31
  fi
28
32
  ```
29
33
 
30
- **If config doesn't exist, STOP IMMEDIATELY. Do not proceed with the workflow.**
34
+ **If config doesn't exist and the feature is NOT `CONFIGURE`, STOP IMMEDIATELY. Do not proceed with the workflow.**
31
35
 
32
36
  Verify that an implementation is complete, correct, and meets feature requirements through multi-layer verification.
33
37