glori-builder 1.0.0 → 1.0.1

package/.claude/CLAUDE.md

@@ -47,6 +47,17 @@ Skip this if:
 - PRs require human approval before merge
 - Max 3 QA failures on an issue before escalating to the user — do not loop forever
 
+## Pipeline Mode — No Stops
+
+Once `/issue-prd` starts the pipeline, run every stage to completion without asking for confirmation, plan review, or approval at any intermediate point. Never ask "does this look right?", "should I proceed?", or "want to review before continuing?"
+
+The only valid reasons to pause:
+- A question only the user can answer (no assumption is reasonable)
+- QA fails 3 times
+- Reviewer flags a Critical security issue
+
+The user should be able to `/issue-prd QUE-123` and immediately start another issue in a parallel session.
+
 ## Stack and Verification
 
 Stack and verification commands live in the **project** `.claude/CLAUDE.md`.

package/.claude/agents/architect.md

@@ -67,3 +67,5 @@ When appending to `.claude/decisions.md`:
 ## Output Contract
 
 `.issue/architecture-decision.md` committed before reporting complete. Memory and decisions updated if anything new was learned.
+
+**Do not ask the orchestrator to review the plan.** Produce it, commit it, report complete. The pipeline continues immediately.

package/.claude/agents/git-workflow.md

@@ -1,6 +1,6 @@
 ---
 name: git-workflow
-description: Git operations specialist. Commits, pushes, and creates PRs to main using squash merge. Never operates without explicit QA pass AND reviewer approval. Use as the final step in the issue pipeline.
+description: Git operations specialist. Commits, pushes, creates PRs, and updates Linear status to PR Ready. Never operates without explicit QA pass AND reviewer approval. Use as the final step in the issue pipeline.
 tools: Bash, Read
 model: haiku
 permissionMode: acceptEdits
@@ -23,9 +23,39 @@ If either is missing, stop and report to the orchestrator.
 1. Stage all changes on the issue branch: `git add -A`
 2. Commit using conventional format (see below)
 3. Push the issue branch: `git push -u origin <branch>`
-4. Create a squash-merge PR to main: `gh pr create --title "..." --body "..." --squash`
-5. Update Linear issue status if instructed by the orchestrator
-6. Report the PR URL to the orchestrator
+4. Create a squash-merge PR to main: `gh pr create --title "..." --body "..."`
+5. Update Linear issue status to the "In Review" or "PR Ready" state (whichever exists for this team)
+6. Add a Linear comment with the PR URL
+7. Report the PR URL to the orchestrator
+
+## Update Linear Status
+
+After the PR is created, find and set the appropriate state. Query the team's states to find one named "PR Ready", "In Review", or similar (type: `inReview`):
+
+```bash
+curl -s -X POST https://api.linear.app/graphql \
+  -H "Authorization: $LINEAR_API_KEY" \
+  -H "Content-Type: application/json" \
+  -d '{"query": "{ team(id: \"TEAM_UUID\") { states { nodes { id name type } } } }"}'
+```
+
+Find the state with type `inReview`. Update the issue:
+
+```bash
+curl -s -X POST https://api.linear.app/graphql \
+  -H "Authorization: $LINEAR_API_KEY" \
+  -H "Content-Type: application/json" \
+  -d '{"query": "mutation { issueUpdate(id: \"ISSUE_UUID\", input: { stateId: \"IN_REVIEW_STATE_ID\" }) { success } }"}'
+```
+
+Add a comment with the PR link:
+
+```bash
+curl -s -X POST https://api.linear.app/graphql \
+  -H "Authorization: $LINEAR_API_KEY" \
+  -H "Content-Type: application/json" \
+  -d '{"query": "mutation { commentCreate(input: { issueId: \"ISSUE_UUID\", body: \"PR ready for review: {PR_URL}\" }) { success } }"}'
+```
 
 ## Commit Format
 

package/.claude/commands/auto-pilot.md

@@ -167,7 +167,8 @@ If CI fails after 2 minutes: treat as QA failure, increment retry counter.
 ### Step 2f: Update status
 
 On **success**:
-- Update Linear issue to Done
+- Find the completed state: query `team.states` and find the state with `type: "completed"` — this is whatever your workspace calls it ("Complete", "Done", etc.)
+- Update Linear issue to that state
 - Update state file: `"status": "complete", "pr": PR_NUMBER`
 - Add Linear comment: "Completed by Glori Builder auto-pilot."
 

package/.claude/commands/issue-prd.md

@@ -50,7 +50,7 @@ Display clearly:
 - **Description**:
   {description}
 
-If the issue state is "In Progress" or "Done", warn the user: "This issue is already {state.name}. Stopping to avoid duplicate work." Then stop.
+If the issue state type is `started` or `completed` (i.e. already in progress or finished), warn the user: "This issue is already {state.name}. Stopping to avoid duplicate work." Then stop.
 
 ### Step 2: Evaluate and Clarify
 
@@ -80,9 +80,27 @@ git branch --show-current
 
 Confirm you are on the feature branch before continuing.
 
-### Step 4: Comment on Linear Issue
+### Step 4: Set Linear Status to In Progress
 
-Add a comment to the Linear issue to mark it as in progress:
+First, get the "In Progress" state ID for this team:
+
+```bash
+curl -s -X POST https://api.linear.app/graphql \
+  -H "Authorization: $LINEAR_API_KEY" \
+  -H "Content-Type: application/json" \
+  -d '{"query": "{ team(id: \"TEAM_UUID\") { states { nodes { id name type } } } }"}'
+```
+
+Find the state with `type: "started"` (this is the In Progress state). Then update the issue:
+
+```bash
+curl -s -X POST https://api.linear.app/graphql \
+  -H "Authorization: $LINEAR_API_KEY" \
+  -H "Content-Type: application/json" \
+  -d '{"query": "mutation { issueUpdate(id: \"ISSUE_UUID\", input: { stateId: \"IN_PROGRESS_STATE_ID\" }) { success issue { state { name } } } }"}'
+```
+
+Then add a comment:
 
 ```bash
 curl -s -X POST https://api.linear.app/graphql \
@@ -91,18 +109,30 @@ curl -s -X POST https://api.linear.app/graphql \
   -d '{"query": "mutation { commentCreate(input: { issueId: \"ISSUE_UUID\", body: \"Pipeline started — architect building implementation plan.\" }) { success } }"}'
 ```
 
-Replace `ISSUE_UUID` with the `id` field (UUID) from the Step 1b response.
+Replace `TEAM_UUID`, `ISSUE_UUID`, and `IN_PROGRESS_STATE_ID` with the values from Steps 1a and 1b.
+
+### Step 5: Hand Off and Run to Completion
 
-### Step 5: Hand Off
+**PIPELINE MODE: do not stop between stages.** Once this step begins, run the full pipeline without asking for confirmation, review, or approval at any intermediate point. The only valid reasons to stop are:
+- A genuine question only the user can answer (no assumptions possible)
+- QA failing 3 times in a row
+- Reviewer flagging a Critical security issue
 
-Tell the orchestrator:
+Tell the orchestrator the pipeline is starting, then immediately invoke each agent in sequence:
 
-> "Issue $ARGUMENTS is ready. Branch: {branch-name}. Starting pipeline: architect → developer(s) → QA → reviewer → git-workflow."
+1. **Architect** — implementation plan, file ownership map, acceptance criteria
+2. **Designer** (if architect flagged `designer_required: true`) — design spec
+3. **Developer(s)** — parallel implementation in separate worktrees
+4. **Merge sub-branches** into feature branch
+5. **QA** — prove green with exit codes (up to 3 retries, fix and rerun on failure)
+6. **Reviewer** — semantic review of full diff (fix and re-QA on rejection)
+7. **git-workflow** — commit, push, squash PR to main
 
-Then invoke the architect agent to create the implementation plan for this issue, passing it the issue title, description, and any clarifications from Step 2.
+Report when PR is created. That is the end of this issue's pipeline.
 
 ## Notes
 - LINEAR_API_KEY must be set as an environment variable
 - The architect creates the implementation PRD — this skill does not
-- If the issue is already In Progress or Done, warn the user and stop
+- If the issue state type is `started` or `completed`, warn the user and stop — check type not name so it works for any workspace ("Complete", "Done", etc.)
+- Never stop mid-pipeline to ask "does this look right?" — produce output and continue
 - Never set the issue to "Queued" — that was the old runner pattern

package/.claude/commands/quetrex-update.md

@@ -1,5 +1,5 @@
 ---
-description: Check for and apply updates to quetrex-base. Shows current vs latest version and updates if behind.
+description: Check for and apply updates to Glori Builder. Shows current vs latest version and updates if behind.
 ---
 
 # Quetrex Update
@@ -7,30 +7,30 @@ description: Check for and apply updates to quetrex-base. Shows current vs lates
 ## Step 1: Check Installed Version
 
 ```bash
-npm list -g @quetrex/base --depth=0 --json 2>/dev/null
+npm list -g glori-builder --depth=0 --json 2>/dev/null
 ```
 
 Extract the installed version from the JSON output.
 
-If `@quetrex/base` is not found in the output, tell the user: "quetrex-base does not appear to be installed globally. Install it with: `npm install -g @quetrex/base`" and stop.
+If `glori-builder` is not found in the output, tell the user: "Glori Builder does not appear to be installed globally. Install it with: `npm install -g glori-builder`" and stop.
 
 ## Step 2: Check Latest Version
 
 ```bash
-npm show @quetrex/base version 2>/dev/null
+npm show glori-builder version 2>/dev/null
 ```
 
 ## Step 3: Compare
 
 If installed == latest:
-> "You're on the latest version of quetrex-base (v{version}). Nothing to do."
+> "You're on the latest version of Glori Builder (v{version}). Nothing to do."
 
 Clear the flag file if it exists: `rm -f ~/.claude/.quetrex-update-available`
 
 Stop.
 
 If installed != latest, display:
-> "quetrex-base update available
+> "Glori Builder update available
 > Installed: v{installed}
 > Latest:    v{latest}
 >
@@ -43,7 +43,7 @@ Wait for confirmation before proceeding.
 ## Step 4: Apply Update
 
 ```bash
-npm install -g @quetrex/base@latest
+npm install -g glori-builder@latest
 ```
 
 The postinstall script runs automatically and copies all updated files to `~/.claude/`.
@@ -52,7 +52,7 @@ The postinstall script runs automatically and copies all updated files to `~/.cl
 
 ```bash
 rm -f ~/.claude/.quetrex-update-available
-npm list -g @quetrex/base --depth=0
+npm list -g glori-builder --depth=0
 ```
 
 Report:

package/.claude/hooks/check-quetrex-update.sh

@@ -1,5 +1,5 @@
 #!/bin/bash
-# Daily background check for quetrex-base updates.
+# Daily background check for Glori Builder updates.
 # Runs on session Stop. Fast exit if checked within 24 hours.
 
 TIMESTAMP_FILE="$HOME/.claude/.quetrex-last-check"
@@ -19,10 +19,10 @@ date +%s > "$TIMESTAMP_FILE"
 
 # Run the npm check in the background so it doesn't delay session exit
 (
-  INSTALLED=$(npm list -g @quetrex/base --depth=0 --json 2>/dev/null \
-    | python3 -c "import json,sys; d=json.load(sys.stdin); print(d.get('dependencies',{}).get('@quetrex/base',{}).get('version',''))" 2>/dev/null)
+  INSTALLED=$(npm list -g glori-builder --depth=0 --json 2>/dev/null \
+    | python3 -c "import json,sys; d=json.load(sys.stdin); print(d.get('dependencies',{}).get('glori-builder',{}).get('version',''))" 2>/dev/null)
 
-  LATEST=$(npm show @quetrex/base version 2>/dev/null)
+  LATEST=$(npm show glori-builder version 2>/dev/null)
 
   if [ -n "$INSTALLED" ] && [ -n "$LATEST" ] && [ "$INSTALLED" != "$LATEST" ]; then
     echo "$LATEST" > "$FLAG_FILE"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "glori-builder",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "description": "Glori Builder — Claude Code base configuration for development teams. Agents, skills, and commands for a complete AI-powered development pipeline.",
   "scripts": {
     "postinstall": "node install.js"