project-iris 0.0.18 → 0.1.0
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.
|
@@ -98,6 +98,13 @@ No project configuration found. This appears to be a new project.
|
|
|
98
98
|
3 - **Ask a question** - Get help without full setup
|
|
99
99
|
```
|
|
100
100
|
|
|
101
|
+
**CRITICAL**: When user selects "Initialize project", the `project-init` skill MUST:
|
|
102
|
+
1. Ask project type question FIRST (full-stack, backend, frontend, CLI, library)
|
|
103
|
+
2. Then detect/ask scenario (greenfield/brownfield/hybrid)
|
|
104
|
+
3. Save `project.yaml` with BOTH fields before proceeding to standards
|
|
105
|
+
|
|
106
|
+
Never skip these questions - they determine which standards are relevant and how Construction works.
|
|
107
|
+
|
|
101
108
|
### Case 2: First-Time User, Existing Code Found (Brownfield)
|
|
102
109
|
|
|
103
110
|
```markdown
|
|
@@ -27,6 +27,22 @@
|
|
|
27
27
|
|
|
28
28
|
---
|
|
29
29
|
|
|
30
|
+
## Display Convention (CRITICAL)
|
|
31
|
+
|
|
32
|
+
When referencing bolt files to the user, ALWAYS show the **bolt ID prominently**, not just "bolt.md":
|
|
33
|
+
|
|
34
|
+
**WRONG**:
|
|
35
|
+
- "Working on bolt.md"
|
|
36
|
+
- "Open bolt.md to see details"
|
|
37
|
+
|
|
38
|
+
**CORRECT**:
|
|
39
|
+
- "Working on **001-extension-foundation**"
|
|
40
|
+
- "Open **001-extension-foundation/bolt.md** to see details"
|
|
41
|
+
|
|
42
|
+
The bolt ID (directory name like `001-extension-foundation`) is the identifier. The file `bolt.md` is just the metadata file inside. Users should always see and understand WHICH bolt they're working on.
|
|
43
|
+
|
|
44
|
+
---
|
|
45
|
+
|
|
30
46
|
## Checkpoints
|
|
31
47
|
|
|
32
48
|
**Checkpoint 1**: Which bolt to work on?
|
|
@@ -33,6 +33,24 @@
|
|
|
33
33
|
|
|
34
34
|
---
|
|
35
35
|
|
|
36
|
+
## Display Convention (CRITICAL)
|
|
37
|
+
|
|
38
|
+
When referencing bolt files to the user, ALWAYS show the **bolt ID prominently**, not just "bolt.md":
|
|
39
|
+
|
|
40
|
+
**WRONG**:
|
|
41
|
+
- "Working on bolt.md"
|
|
42
|
+
- "Updating bolt.md status"
|
|
43
|
+
- "Approve changes to bolt.md?"
|
|
44
|
+
|
|
45
|
+
**CORRECT**:
|
|
46
|
+
- "Working on **001-extension-foundation**"
|
|
47
|
+
- "Updating **001-extension-foundation** status"
|
|
48
|
+
- "Approve changes to **001-extension-foundation/bolt.md**?"
|
|
49
|
+
|
|
50
|
+
The bolt ID (directory name like `001-extension-foundation`) is the identifier. Users should always see and understand WHICH bolt they're working on.
|
|
51
|
+
|
|
52
|
+
---
|
|
53
|
+
|
|
36
54
|
## Bolt Type Execution
|
|
37
55
|
|
|
38
56
|
Stages, activities, outputs, and checkpoints come from the bolt type definition:
|
|
@@ -430,6 +448,24 @@ If construction log doesn't exist, create it using template:
|
|
|
430
448
|
|
|
431
449
|
---
|
|
432
450
|
|
|
451
|
+
## CRITICAL: Post-Bolt Options (NEVER SKIP)
|
|
452
|
+
|
|
453
|
+
**After EVERY bolt completion, you MUST present the Actions menu above.**
|
|
454
|
+
|
|
455
|
+
```text
|
|
456
|
+
┌─────────────────────────────────────────────────────────────┐
|
|
457
|
+
│ BOLT COMPLETED │
|
|
458
|
+
│ → You MUST show the Actions menu (1-next, 2-list, 3-ops) │
|
|
459
|
+
│ → Do NOT just ask "approve to continue?" │
|
|
460
|
+
│ → Let the user CHOOSE their next action │
|
|
461
|
+
└─────────────────────────────────────────────────────────────┘
|
|
462
|
+
```
|
|
463
|
+
|
|
464
|
+
**Failure Mode**: Asking "Ready to proceed to next bolt?" without showing options
|
|
465
|
+
**Correct Behavior**: Always show numbered Actions list and wait for user choice
|
|
466
|
+
|
|
467
|
+
---
|
|
468
|
+
|
|
433
469
|
## Bolt Completion Checklist
|
|
434
470
|
|
|
435
471
|
**Use this checklist to verify all completion tasks are done:**
|
package/lib/constants.js
CHANGED
|
@@ -1,14 +1,18 @@
|
|
|
1
1
|
|
|
2
|
-
|
|
2
|
+
/**
|
|
3
|
+
* OSiris Brand Palette: "The Digital Temple"
|
|
4
|
+
* Strategy: High-contrast Dark Mode for Enterprise Traceability.
|
|
5
|
+
* Persona: Architect/Engineer
|
|
6
|
+
*/
|
|
3
7
|
const THEME_COLORS = {
|
|
4
|
-
primary: '#
|
|
5
|
-
secondary: '#
|
|
6
|
-
accent: '#
|
|
7
|
-
success: '#
|
|
8
|
-
error: '#
|
|
9
|
-
warning: '#
|
|
10
|
-
info: '#
|
|
11
|
-
dim: '#
|
|
8
|
+
primary: '#0B0E14', // Deep Obsidian (The System Foundation / Background)
|
|
9
|
+
secondary: '#1F2937', // Architectural Slate (The Repository / UI Surfaces)
|
|
10
|
+
accent: '#EAB308', // Osiris Gold (The Intent / AI Intelligence Spark)
|
|
11
|
+
success: '#10B981', // Emerald Trace (Verified Code / Completed Intent)
|
|
12
|
+
error: '#EF4444', // Pulse Red (System Error / Intent Mismatch)
|
|
13
|
+
warning: '#F59E0B', // Solar Amber (Validation Required / Pending Action)
|
|
14
|
+
info: '#0EA5E9', // Cyber Cyan (Technical Metadata / AWS Context)
|
|
15
|
+
dim: '#64748B' // Muted Steel (Inactive Threads / Non-essential Grid Lines)
|
|
12
16
|
};
|
|
13
17
|
|
|
14
18
|
const FLOWS = {
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "project-iris",
|
|
3
|
-
"version": "0.0
|
|
3
|
+
"version": "0.1.0",
|
|
4
4
|
"description": "Multi-agent orchestration system for AI-native software development. Delivers AI-DLC, Agile, and custom SDLC flows as markdown-based agent systems.",
|
|
5
5
|
"main": "lib/installer.js",
|
|
6
6
|
"bin": {
|