@sixsevenai/ai-dlc-installer 1.5.0 → 1.5.1

package/library/commands/ai-dlc/cheatsheet.md

@@ -1,63 +1,63 @@
----
-command: ai-dlc:cheatsheet
-description: Display a quick-reference card of all AI-DLC slash commands organized by phase
-phase: cross-cutting
-allowed-tools: Read
----
-
-# AI-DLC Cheatsheet
-
-Output the following quick-reference card directly to the user. Do not add commentary — just present the card as-is in a single, readable block.
-
----
-
-```
-AI-DLC Quick Reference
-======================
-
-INCEPTION FLOW
-  /ai-dlc:start-intent       Define business intent (WHAT and WHY)
-  /ai-dlc:create-units        Decompose into atomic Units
-  /ai-dlc:generate-stories    Create INVEST user stories
-  /ai-dlc:elicit-nfrs         Define non-functional requirements
-  /ai-dlc:assess-risks        Identify risks and mitigations
-  /ai-dlc:plan-bolt           Estimate work in 1-3 day Bolts
-  /ai-dlc:validate-phase inception   Verify phase completeness
-
-CONSTRUCTION FLOW
-  /ai-dlc:domain-model        DDD domain modeling
-  /ai-dlc:logical-design      Architecture and ADRs
-  /ai-dlc:design-api          OpenAPI contract design
-  /ai-dlc:generate-code       Production code generation
-  /ai-dlc:build-tests         Test suite generation
-  /ai-dlc:review-code         7-dimension code review
-  /ai-dlc:validate-phase construction   Verify phase completeness
-
-OPERATIONS FLOW
-  /ai-dlc:package-unit        Create deployment artifacts
-  /ai-dlc:deploy              Deploy to environment
-  /ai-dlc:setup-monitoring    Configure observability
-  /ai-dlc:create-runbook      Incident response procedures
-  /ai-dlc:validate-phase operations   Verify phase completeness
-
-UTILITY COMMANDS
-  /ai-dlc:status              Show current phase and progress
-  /ai-dlc:next-phase          Transition to next phase
-  /ai-dlc:archive-session     Archive completed work
-  /ai-dlc:talk                Interactive training with AI-DLC expert
-  /ai-dlc:quickstart          Guided onboarding (~5 min)
-
-COMPANION: SPECKIT (spec-driven development)
-  /spec:specify               Create feature specification
-  /spec:clarify               Fill spec gaps with questions
-  /spec:plan                  Generate implementation plan
-  /spec:tasks                 Generate dependency-ordered tasks
-  /spec:implement             Execute tasks from tasks.md
-  /spec:to-intent             Bridge spec to AI-DLC intent
-
-COMPANION: TASK (lightweight task planning)
-  /task:plan                  Decompose prompt into task plan
-  /task:execute               Execute plan step-by-step
-  /task:clarify               Refine plan with questions
-  /task:complete              Finalize with Complete.md + commit
-```
+---
+command: ai-dlc:cheatsheet
+description: Display a quick-reference card of all AI-DLC slash commands organized by phase
+phase: cross-cutting
+allowed-tools: Read
+---
+
+# AI-DLC Cheatsheet
+
+Output the following quick-reference card directly to the user. Do not add commentary — just present the card as-is in a single, readable block.
+
+---
+
+```
+AI-DLC Quick Reference
+======================
+
+INCEPTION FLOW
+  /ai-dlc:start-intent       Define business intent (WHAT and WHY)
+  /ai-dlc:create-units        Decompose into atomic Units
+  /ai-dlc:generate-stories    Create INVEST user stories
+  /ai-dlc:elicit-nfrs         Define non-functional requirements
+  /ai-dlc:assess-risks        Identify risks and mitigations
+  /ai-dlc:plan-bolt           Estimate work in 1-3 day Bolts
+  /ai-dlc:validate-phase inception   Verify phase completeness
+
+CONSTRUCTION FLOW
+  /ai-dlc:domain-model        DDD domain modeling
+  /ai-dlc:logical-design      Architecture and ADRs
+  /ai-dlc:design-api          OpenAPI contract design
+  /ai-dlc:generate-code       Production code generation
+  /ai-dlc:build-tests         Test suite generation
+  /ai-dlc:review-code         7-dimension code review
+  /ai-dlc:validate-phase construction   Verify phase completeness
+
+OPERATIONS FLOW
+  /ai-dlc:package-unit        Create deployment artifacts
+  /ai-dlc:deploy              Deploy to environment
+  /ai-dlc:setup-monitoring    Configure observability
+  /ai-dlc:create-runbook      Incident response procedures
+  /ai-dlc:validate-phase operations   Verify phase completeness
+
+UTILITY COMMANDS
+  /ai-dlc:status              Show current phase and progress
+  /ai-dlc:next-phase          Transition to next phase
+  /ai-dlc:archive-session     Archive completed work
+  /ai-dlc:talk                Interactive training with AI-DLC expert
+  /ai-dlc:quickstart          Guided onboarding (~5 min)
+
+COMPANION: SPECKIT (spec-driven development)
+  /spec:specify               Create feature specification
+  /spec:clarify               Fill spec gaps with questions
+  /spec:plan                  Generate implementation plan
+  /spec:tasks                 Generate dependency-ordered tasks
+  /spec:implement             Execute tasks from tasks.md
+  /spec:to-intent             Bridge spec to AI-DLC intent
+
+COMPANION: TASK (lightweight task planning)
+  /task:plan                  Decompose prompt into task plan
+  /task:execute               Execute plan step-by-step
+  /task:clarify               Refine plan with questions
+  /task:complete              Finalize with Complete.md + commit
+```

package/library/commands/ai-dlc/construct-unit.md

@@ -57,6 +57,20 @@ Has UI: ${has-ui !== false}
 Has API: ${has-api !== false}
 Has DB: ${has-db || false}
 
+<auto-detection>
+**IMPORTANT — Flag Auto-Detection:**
+Before starting, run `ai-dlc prepare ai-dlc:construct-unit --unit ${unit-name}` and check the `suggestedDesignSteps` array in the JSON response.
+
+If the user did NOT explicitly pass `--has-ui`, `--has-api`, or `--has-db` flags, use the CLI's detection results:
+- **high confidence** suggestions → treat as if the flag was set to `true`
+- **medium confidence** suggestions → treat as if the flag was set to `true`, but note it was auto-detected
+- **low confidence** suggestions → skip unless you independently confirm the need after reading artifacts
+
+If the user DID explicitly pass a flag, that flag always takes precedence over auto-detection.
+
+Log which design steps were auto-detected vs explicitly requested so the user can see what happened.
+</auto-detection>
+
 Execute the complete Construction workflow:
 
 <execution-steps>

package/library/commands/ai-dlc/quickstart.md

@@ -1,150 +1,150 @@
----
-command: ai-dlc:quickstart
-description: Interactive 5-minute onboarding walkthrough for new AI-DLC users — covers core concepts, runs your first Intent, and shows next steps
-argument-hint: ""
-phase: cross-cutting
-allowed-tools: Task, Read, AskUserQuestion
-args: []
----
-
-# AI-DLC Quickstart
-
-A guided, conversational onboarding flow for new team members. Covers the three phases, core concepts, and walks you through creating your first Intent.
-
-## Command: /ai-dlc:quickstart
-
-## Context Isolation: Required
-
-**MANDATORY**: Use the Task tool to spawn the ai-dlc-trainer subagent. Do NOT execute the walkthrough in this context.
-
-Use Task tool with these parameters:
-- **subagent_type**: `ai-dlc-trainer`
-- **prompt**: See below
-
-## Subagent Prompt
-
-```
-You are running the AI-DLC Quickstart walkthrough for a new user. Keep everything concise and actionable — aim for ~5 minutes total.
-
-Follow these steps IN ORDER. After each step, pause and let the user respond before continuing.
-
----
-
-STEP 1: WELCOME AND OVERVIEW
-
-Print exactly:
-
-## Welcome to AI-DLC
-
-**AI-DLC** (AI-Driven Lifecycle) replaces the traditional SDLC with three phases:
-
-| Phase | Purpose | Key Output |
-|-------|---------|------------|
-| **Inception** | Define WHAT and WHY | Intent, Units, Stories, NFRs, Risks, Bolt Plan |
-| **Construction** | Build production software | Domain Models, Code, Tests, Reviews |
-| **Operations** | Deploy, monitor, maintain | Deployments, Monitoring, Runbooks |
-
-**Two concepts to know:**
-- **Unit** — An atomic work item estimated at 1-3 Bolts
-- **Bolt** — A 1-3 day timebox that delivers a tangible artifact
-
-Every project starts with an **Intent** — a plain-language statement of your business goal.
-
-Then ask: "Ready to create your first Intent? (yes / I have questions first)"
-
-If the user has questions, answer them briefly, then proceed.
-
----
-
-STEP 2: CREATE YOUR FIRST INTENT
-
-Say:
-
-Let's start Inception. Run this command now:
-
-```
-/ai-dlc:start-intent "Build a task management app for small teams"
-```
-
-Or replace the text in quotes with your own idea. I'll wait while you run it.
-
-Wait for the user to confirm they ran it.
-
----
-
-STEP 3: CHECK YOUR PROGRESS
-
-Say:
-
-Now let's see what AI-DLC recorded. Run:
-
-```
-/ai-dlc:status
-```
-
-This shows your current phase, active session, and completed artifacts. You should see your new Intent listed under Inception.
-
-Wait for the user to confirm.
-
----
-
-STEP 4: EXPLAIN NEXT STEPS
-
-Print exactly:
-
-## What Comes Next
-
-With your Intent created, here is the Inception sequence:
-
-1. `/ai-dlc:create-units` — Break your Intent into Units
-2. `/ai-dlc:generate-stories` — Create user stories for each Unit
-3. `/ai-dlc:elicit-nfrs` — Capture non-functional requirements
-4. `/ai-dlc:assess-risks project` — Identify risks and mitigations
-5. `/ai-dlc:plan-bolt` — Estimate each Unit in Bolts
-6. `/ai-dlc:validate-phase inception` — Confirm Inception is complete
-
-Once Inception passes validation, run `/ai-dlc:next-phase` to move into Construction.
-
-**Alternative:** Use `/ai-dlc:mob-elaborate` for a single collaborative session that produces Units, NFRs, and Risks together.
-
----
-
-STEP 5: POINT TO DEEPER RESOURCES
-
-Say:
-
-## Resources
-
-- **Getting Started Guide**: Read `.claude/docs/GETTING-STARTED-GUIDE.md` for a full walkthrough
-- **Ask the Expert**: Run `/ai-dlc:talk` to chat with Dr. Alex Chen about methodology
-- **Agent Directory**: Run `/agent-directory` to see all 58 specialized agents
-- **Status Anytime**: Run `/ai-dlc:status` to see where you are
-
-You're all set. Run `/ai-dlc:create-units` to continue, or ask me anything.
-
----
-
-End the session after Step 5 unless the user asks follow-up questions.
-```
-
-## Usage Examples
-
-```bash
-/ai-dlc:quickstart
-```
-
-## What You'll Learn
-
-- **Core Concepts**: Phases, Units, and Bolts
-- **First Command**: Create an Intent hands-on
-- **Status Check**: See your progress in AI-DLC
-- **Next Steps**: The full Inception command sequence
-- **Resources**: Where to learn more
-
-## Prerequisites
-
-None — designed for first-time users.
-
-## Duration
-
-Approximately 5 minutes.
+---
+command: ai-dlc:quickstart
+description: Interactive 5-minute onboarding walkthrough for new AI-DLC users — covers core concepts, runs your first Intent, and shows next steps
+argument-hint: ""
+phase: cross-cutting
+allowed-tools: Task, Read, AskUserQuestion
+args: []
+---
+
+# AI-DLC Quickstart
+
+A guided, conversational onboarding flow for new team members. Covers the three phases, core concepts, and walks you through creating your first Intent.
+
+## Command: /ai-dlc:quickstart
+
+## Context Isolation: Required
+
+**MANDATORY**: Use the Task tool to spawn the ai-dlc-trainer subagent. Do NOT execute the walkthrough in this context.
+
+Use Task tool with these parameters:
+- **subagent_type**: `ai-dlc-trainer`
+- **prompt**: See below
+
+## Subagent Prompt
+
+```
+You are running the AI-DLC Quickstart walkthrough for a new user. Keep everything concise and actionable — aim for ~5 minutes total.
+
+Follow these steps IN ORDER. After each step, pause and let the user respond before continuing.
+
+---
+
+STEP 1: WELCOME AND OVERVIEW
+
+Print exactly:
+
+## Welcome to AI-DLC
+
+**AI-DLC** (AI-Driven Lifecycle) replaces the traditional SDLC with three phases:
+
+| Phase | Purpose | Key Output |
+|-------|---------|------------|
+| **Inception** | Define WHAT and WHY | Intent, Units, Stories, NFRs, Risks, Bolt Plan |
+| **Construction** | Build production software | Domain Models, Code, Tests, Reviews |
+| **Operations** | Deploy, monitor, maintain | Deployments, Monitoring, Runbooks |
+
+**Two concepts to know:**
+- **Unit** — An atomic work item estimated at 1-3 Bolts
+- **Bolt** — A 1-3 day timebox that delivers a tangible artifact
+
+Every project starts with an **Intent** — a plain-language statement of your business goal.
+
+Then ask: "Ready to create your first Intent? (yes / I have questions first)"
+
+If the user has questions, answer them briefly, then proceed.
+
+---
+
+STEP 2: CREATE YOUR FIRST INTENT
+
+Say:
+
+Let's start Inception. Run this command now:
+
+```
+/ai-dlc:start-intent "Build a task management app for small teams"
+```
+
+Or replace the text in quotes with your own idea. I'll wait while you run it.
+
+Wait for the user to confirm they ran it.
+
+---
+
+STEP 3: CHECK YOUR PROGRESS
+
+Say:
+
+Now let's see what AI-DLC recorded. Run:
+
+```
+/ai-dlc:status
+```
+
+This shows your current phase, active session, and completed artifacts. You should see your new Intent listed under Inception.
+
+Wait for the user to confirm.
+
+---
+
+STEP 4: EXPLAIN NEXT STEPS
+
+Print exactly:
+
+## What Comes Next
+
+With your Intent created, here is the Inception sequence:
+
+1. `/ai-dlc:create-units` — Break your Intent into Units
+2. `/ai-dlc:generate-stories` — Create user stories for each Unit
+3. `/ai-dlc:elicit-nfrs` — Capture non-functional requirements
+4. `/ai-dlc:assess-risks project` — Identify risks and mitigations
+5. `/ai-dlc:plan-bolt` — Estimate each Unit in Bolts
+6. `/ai-dlc:validate-phase inception` — Confirm Inception is complete
+
+Once Inception passes validation, run `/ai-dlc:next-phase` to move into Construction.
+
+**Alternative:** Use `/ai-dlc:mob-elaborate` for a single collaborative session that produces Units, NFRs, and Risks together.
+
+---
+
+STEP 5: POINT TO DEEPER RESOURCES
+
+Say:
+
+## Resources
+
+- **Getting Started Guide**: Read `.claude/docs/GETTING-STARTED-GUIDE.md` for a full walkthrough
+- **Ask the Expert**: Run `/ai-dlc:talk` to chat with Dr. Alex Chen about methodology
+- **Agent Directory**: Run `/agent-directory` to see all 58 specialized agents
+- **Status Anytime**: Run `/ai-dlc:status` to see where you are
+
+You're all set. Run `/ai-dlc:create-units` to continue, or ask me anything.
+
+---
+
+End the session after Step 5 unless the user asks follow-up questions.
+```
+
+## Usage Examples
+
+```bash
+/ai-dlc:quickstart
+```
+
+## What You'll Learn
+
+- **Core Concepts**: Phases, Units, and Bolts
+- **First Command**: Create an Intent hands-on
+- **Status Check**: See your progress in AI-DLC
+- **Next Steps**: The full Inception command sequence
+- **Resources**: Where to learn more
+
+## Prerequisites
+
+None — designed for first-time users.
+
+## Duration
+
+Approximately 5 minutes.

package/library/commands/git/branch-report.md

@@ -0,0 +1,176 @@
+---
+command: git:branch-report
+description: List git branches with dates, commit messages, and behind/ahead tracking
+argument-hint: "[--local] [--online] [--path <dir>]"
+phase: cross-cutting
+allowed-tools: Bash, Read
+args:
+  - name: --local
+    description: List local branches (default if no flag specified)
+    required: false
+  - name: --online
+    description: List remote origin branches
+    required: false
+  - name: --path
+    description: Path to another git repository to report on
+    required: false
+---
+
+# Branch Report
+
+List git branches with rich metadata including last commit date, commit message, and behind/ahead counts.
+
+## Command: /git:branch-report [--local|--online] [--path <dir>]
+
+## Execution Protocol
+
+### Step 1: Resolve Target Directory
+
+- Parse arguments. If `--path <dir>` is provided, set `GIT_DIR_FLAG="-C <dir>"`, otherwise `GIT_DIR_FLAG=""`.
+- Validate the path is a git repo:
+```bash
+git $GIT_DIR_FLAG rev-parse --git-dir 2>/dev/null
+```
+- If validation fails, report error: "Not a git repository: <dir>" and stop.
+
+### Step 2: Determine Mode
+
+- If `--online` is specified, set MODE to "remote"
+- Otherwise (default, or `--local`), set MODE to "local"
+
+### Step 3: Detect Default Branch
+
+Run these commands to auto-detect the default branch name:
+```bash
+# Try symbolic ref first
+git $GIT_DIR_FLAG symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@'
+
+# Fallback: check if main exists
+git $GIT_DIR_FLAG show-ref --verify --quiet refs/heads/main 2>/dev/null && echo "main"
+
+# Fallback: check if master exists
+git $GIT_DIR_FLAG show-ref --verify --quiet refs/heads/master 2>/dev/null && echo "master"
+```
+Use the first successful result as `DEFAULT_BRANCH`.
+
+### Step 4: Fetch Remote (online mode only)
+
+If MODE is "remote":
+```bash
+git $GIT_DIR_FLAG fetch origin --prune
+```
+
+### Step 5: List Branches
+
+**For local mode** (`refs/heads/`):
+```bash
+git $GIT_DIR_FLAG for-each-ref --sort=-committerdate refs/heads/ \
+  --format='%(HEAD)|%(refname:short)|%(committerdate:relative)|%(subject)'
+```
+
+**For online mode** (`refs/remotes/origin/`):
+```bash
+git $GIT_DIR_FLAG for-each-ref --sort=-committerdate refs/remotes/origin/ \
+  --format='%(refname:short)|%(committerdate:relative)|%(subject)' \
+  | grep -v 'origin/HEAD'
+```
+
+### Step 6: Calculate Behind/Ahead
+
+For each branch from Step 5, calculate behind/ahead relative to the default branch:
+
+**Local mode:**
+```bash
+git $GIT_DIR_FLAG rev-list --left-right --count $DEFAULT_BRANCH...<branch> 2>/dev/null
+```
+Output format: `<behind>\t<ahead>`
+
+**Online mode:**
+```bash
+git $GIT_DIR_FLAG rev-list --left-right --count origin/$DEFAULT_BRANCH...<branch> 2>/dev/null
+```
+
+If the command fails (e.g., unrelated histories), show `-` for both values.
+
+### Step 7: Format Output
+
+Display a header, then render results as a clean columnar table with a horizontal rule under the header:
+
+```
+Branch Report (local) — repo: <repo-name>
+Default branch: <DEFAULT_BRANCH>
+
+    Branch                              Age              Behind   Ahead   Last Commit
+    ─────────────────────────────────   ──────────────   ──────   ─────   ──────────────────────────────────────────────
+ *  main                                2 hours ago          —       —   feat: add new dashboard widget
+    ─────────────────────────────────   ──────────────   ──────   ─────   ──────────────────────────────────────────────
+    feature/auth-refactor               3 days ago          12       5   fix: token refresh edge case
+    ─────────────────────────────────   ──────────────   ──────   ─────   ──────────────────────────────────────────────
+    hotfix/login-crash                  1 week ago          25       2   hotfix: null check on login response
+    ─────────────────────────────────   ──────────────   ──────   ─────   ──────────────────────────────────────────────
+    stale/old-experiment                3 months ago       142       1   experiment: try new caching approach
+    ─────────────────────────────────   ──────────────   ──────   ─────   ──────────────────────────────────────────────
+
+4 branches | 3 ahead of main | 4 behind main
+```
+
+- No outer border or vertical pipe characters — just aligned columns with space padding
+- Horizontal rule (`─`) under each column header AND between every row for grid-like readability
+- `*` in the left margin indicates current branch (local mode only)
+- Behind/Ahead columns right-aligned; use `—` (em dash) for the default branch row
+- Truncate commit message to 50 characters, append `...` if truncated
+- Sort by most recent commit date (descending) — already handled by `--sort=-committerdate`
+- Summary line below the table with branch counts
+- For online mode, header says "Branch Report (remote)" instead of "(local)"
+
+## Usage Examples
+
+```bash
+# List local branches (default)
+/git:branch-report
+
+# Explicitly local
+/git:branch-report --local
+
+# List remote branches
+/git:branch-report --online
+
+# Report on a different repository
+/git:branch-report --path /c/dev/other-project
+
+# Remote branches of another repo
+/git:branch-report --online --path /c/dev/other-project
+```
+
+## Sample Output
+
+```
+Branch Report (local) — repo: SixSevenAI
+Default branch: main
+
+    Branch                              Age              Behind   Ahead   Last Commit
+    ─────────────────────────────────   ──────────────   ──────   ─────   ──────────────────────────────────────────────
+ *  hotfix/cli-false-complete           2 hours ago          0       2   fix(cli): use unit-based completion for status
+    ─────────────────────────────────   ──────────────   ──────   ─────   ──────────────────────────────────────────────
+    feature/workflow-engine             1 day ago            5       8   feat: add workflow pause/resume support
+    ─────────────────────────────────   ──────────────   ──────   ─────   ──────────────────────────────────────────────
+    feature/agent-voting                3 days ago          12       3   feat: implement MAKER voting consensus
+    ─────────────────────────────────   ──────────────   ──────   ─────   ──────────────────────────────────────────────
+    bugfix/session-archive              1 week ago          20       1   fix: archive metadata generation
+    ─────────────────────────────────   ──────────────   ──────   ─────   ──────────────────────────────────────────────
+    experiment/mcp-bridge               2 months ago        87       4   experiment: MCP server bridge prototype
+    ─────────────────────────────────   ──────────────   ──────   ─────   ──────────────────────────────────────────────
+
+5 branches | 4 ahead of main | 4 behind main
+```
+
+## Prerequisites
+
+- Git repository (local or specified via `--path`)
+- For `--online`: network access to fetch from origin
+
+## Related Commands
+
+- `/git:branch-validate` — Deep comparison of a branch against another
+- `/git:check-duplicates` — Analyze changed files for semantic duplicates
+- `/commit` — Intelligent commit workflow