@devobsessed/code-captain 0.2.2 → 0.3.2

package/bin/install.js

@@ -444,6 +444,16 @@ class CodeCaptainInstaller {
     return recommendations;
   }
 
+  // Detect .sln files in the current directory
+  async detectSlnFiles() {
+    try {
+      const entries = await fs.readdir(".");
+      return entries.filter((entry) => entry.endsWith(".sln"));
+    } catch {
+      return [];
+    }
+  }
+
   // Auto-detect IDE preference
   detectIDE() {
     const detections = [];
@@ -527,9 +537,33 @@ class CodeCaptainInstaller {
     const changeInfo = await this.detectChanges(selectedIDE);
 
     if (changeInfo.isFirstInstall) {
-      // Fresh installation - install everything
+      // Fresh installation - install everything, but check for VS Solution View opt-in
+      let installVsSolution = false;
+      if (selectedIDE === "copilot") {
+        // Auto-detect .sln files to determine if VS Solution View is relevant
+        const slnFiles = await this.detectSlnFiles();
+        if (slnFiles.length > 0) {
+          console.log(
+            chalk.green(
+              `\n✨ Detected .NET solution file(s): ${slnFiles.join(", ")}`
+            )
+          );
+          const { enableVsSolution } = await inquirer.prompt([
+            {
+              type: "confirm",
+              name: "enableVsSolution",
+              message:
+                "Install VS Solution View (Directory.Build.props) to make Code Captain files visible in Visual Studio Solution Explorer?",
+              default: true,
+            },
+          ]);
+          installVsSolution = enableVsSolution;
+        }
+      }
+
       return {
         installAll: true,
+        installVsSolution,
         changeInfo,
       };
     }
@@ -1111,13 +1145,15 @@ class CodeCaptainInstaller {
         spinner.text = `Installing files... (${completed}/${files.length})`;
       }
 
-      // Handle Directory.Build.props for vs-solution component (opt-in only, not in installAll)
+      // Handle Directory.Build.props for vs-solution component
       let vsSolutionResult = null;
-      if (
-        !installOptions.installAll &&
-        selectedComponents &&
-        selectedComponents.includes("vs-solution")
-      ) {
+      const shouldInstallVsSolution =
+        (installOptions.installAll && installOptions.installVsSolution) ||
+        (!installOptions.installAll &&
+          selectedComponents &&
+          selectedComponents.includes("vs-solution"));
+
+      if (shouldInstallVsSolution) {
         spinner.text = "Installing Directory.Build.props...";
         vsSolutionResult = await this.installDirectoryBuildProps();
       }

package/copilot/Directory.Build.props

@@ -1,8 +1,10 @@
 <Project>
-  <!-- Code Captain: Make .github/ Copilot files visible in VS Solution Explorer -->
+  <!-- Code Captain: Make Copilot and Code Captain files visible in VS Solution Explorer -->
   <ItemGroup Label="Code Captain">
     <None Include=".github\copilot-instructions.md" Link="Code Captain\copilot-instructions.md" />
     <None Include=".github\agents\**\*" Link="Code Captain\agents\%(RecursiveDir)%(Filename)%(Extension)" />
     <None Include=".github\prompts\**\*" Link="Code Captain\prompts\%(RecursiveDir)%(Filename)%(Extension)" />
+    <None Include=".code-captain\docs\**\*" Link="Code Captain\docs\%(RecursiveDir)%(Filename)%(Extension)" />
+    <None Include=".code-captain\specs\**\*" Link="Code Captain\specs\%(RecursiveDir)%(Filename)%(Extension)" />
   </ItemGroup>
 </Project>

package/copilot/copilot-instructions.md

@@ -17,8 +17,34 @@ When a user invokes any Code Captain command, you MUST:
    - "Steady as she goes! Code Captain prepared to steer your project to success."
    - "Anchors aweigh! Code Captain ready to lead your development expedition."
    - "All hands on deck! Code Captain here to guide your coding voyage."
-2. **Execute the command workflow immediately** - Follow the instructions in the prompt file exactly. Do NOT describe or summarize the instructions back to the user. Act on them.
-3. **Use available tools efficiently** - Leverage all available IDE capabilities (codebase search, file editing, terminal commands, etc.)
+2. **Locate the repository root (mandatory)** - Before accessing any `.code-captain/` path or executing any command workflow, confirm you are at the repository root. See **Working Directory Bootstrap** below.
+3. **Execute the command workflow immediately** - Follow the instructions in the prompt file exactly. Do NOT describe or summarize the instructions back to the user. Act on them.
+4. **Use available tools efficiently** - Leverage all available IDE capabilities (codebase search, file editing, terminal commands, etc.)
+
+## Working Directory Bootstrap
+
+IDEs may open the terminal in a sub-project directory instead of the repository root (common with Visual Studio + .NET solutions). The `.code-captain/` folder lives at the repo root, so you MUST locate it before any file access or terminal command that references `.code-captain/`.
+
+**Detection steps (run once at the start of every command):**
+
+1. **Prefer tool-based search (no shell dependency)** — Use `codebase` or `search` to look for `.code-captain/` or `.git/`. These tools work regardless of shell type or OS. If the repo root is found this way, record the path and skip to step 5.
+2. **If terminal fallback is needed, detect the shell first** — Run this single command via `runCommands`:
+   ```
+   echo $PSVersionTable
+   ```
+   - If the output contains version info (e.g., `PSVersion`), the shell is **PowerShell** (typical: Windows + Visual Studio).
+   - If the output is blank or errors, the shell is **bash/zsh** (typical: macOS, Linux, VS Code on any OS).
+   - **Record the detected shell type** and use only the matching syntax for all subsequent commands in this session.
+3. **Check for `.code-captain/` in the current directory:**
+   - **PowerShell:** `if (Test-Path .code-captain) { 'FOUND' } else { 'NOT_FOUND' }`
+   - **Bash/Zsh:** `test -d .code-captain && echo FOUND || echo NOT_FOUND`
+4. If `NOT_FOUND`, navigate to the parent directory and check again. Repeat up to 3 levels:
+   - **PowerShell:** `Set-Location .. ; if (Test-Path .code-captain) { Get-Location } else { 'NOT_FOUND' }`
+   - **Bash/Zsh:** `cd .. && test -d .code-captain && pwd || echo NOT_FOUND`
+5. Once the root is found, **record the repo root path** and prefix all `.code-captain/` references with that path for the remainder of the session.
+6. If `.code-captain/` is not found after 3 levels, inform the user: "Could not locate the .code-captain directory. Please ensure you opened the repository root folder in your IDE, or run `/initialize` to create the project foundation."
+
+**Important:** Do NOT skip this step even if you assume you are at the root. The one-time cost of verification prevents repeated failures and retries.
 
 ## File Organization
 
@@ -53,6 +79,35 @@ All Code Captain output is organized under `.code-captain/`:
 ### Meta
 - `new-command` - Create new Code Captain commands following established patterns
 
+## Terminal Command Standards
+
+When executing terminal commands via `runCommands`:
+
+1. **Non-interactive only** — Never run commands that require user input or enter watch/interactive mode
+   - Vitest: `npx vitest run` (never bare `npx vitest` which enters watch mode)
+   - Jest: `npx jest --ci`
+   - dotnet: `dotnet test` (already non-interactive)
+2. **No long-running processes** — Never start dev servers, file watchers, or background services through `runCommands`. They will block the chat session indefinitely.
+3. **CWD preservation** — Use single-expression commands when working in subdirectories: `cd <subdir> && <command>`. Never leave the terminal in a shifted working directory. All `.code-captain/` paths are relative to the repository root.
+4. **Quick verification** — Prefer non-blocking checks over full builds. Use `--dry-run`, `--no-restore`, or type-check-only flags when assessing project health.
+5. **Verify before using npm scripts** — If a `package.json` `test` or `build` script exists, check its contents before running it. Scripts may invoke watch mode or dev servers.
+6. **Detect the shell before running commands** — The shell type varies by IDE and OS. The Working Directory Bootstrap detects this once per session. Use the detected shell type for all commands:
+   - **Windows + Visual Studio:** Typically PowerShell. Uses `Test-Path`, `Set-Location`, `Get-ChildItem`, and `;` to chain statements.
+   - **macOS / Linux (any IDE):** Typically zsh or bash. Uses `test -d`, `cd`, `ls`, and `&&` to chain statements. PowerShell is NOT available unless explicitly installed.
+   - **Windows + VS Code:** Usually PowerShell, but may be configured to use Git Bash, WSL, or CMD.
+   - **Path separators:** Always use `/` (forward slash) — it works in PowerShell, bash, and zsh.
+   - **When in doubt:** Prefer tool-based operations (`codebase`, `search`, `editFiles`) over terminal commands. Tools are shell-independent.
+
+## Monorepo & Solution Awareness
+
+Projects may contain multiple sub-projects (e.g., .NET solutions with React frontends). When working in these projects:
+
+1. **Repo root is already known** — The Working Directory Bootstrap (above) has already located the repo root. Use that recorded path for all `.code-captain/` references.
+2. **Detect project topology early** — Look for `.sln` files, multiple `package.json` files, or workspace configurations (`pnpm-workspace.yaml`, `lerna.json`, `nx.json`). This tells you the project has subdirectories with independent tooling.
+3. **Identify the target subdirectory** — Determine which sub-project contains the code relevant to the current task. Note its path relative to the repo root.
+4. **Root-relative file references** — All `.code-captain/` paths (specs, progress trackers, docs) are relative to the repository root, not any subdirectory. When running terminal commands in a subdirectory, always return to or reference the repo root path for `.code-captain/` operations.
+5. **Subdirectory-specific tooling** — Each sub-project may have its own `package.json`, test runner, build tool, and configuration. Don't assume the root-level tooling applies to subdirectories.
+
 ## Behavioral Rules
 
 - **Challenge ideas** - If a requirement seems technically infeasible, the scope is too large, or the approach conflicts with existing patterns, say so directly. Suggest alternatives.

package/copilot/prompts/create-adr.prompt.md

@@ -21,53 +21,51 @@ Your mission: Create a comprehensive Architecture Decision Record (ADR) that doc
 
 ## Prerequisites
 
-**MANDATORY:** Automatically execute research if no relevant research exists. The ADR creation process will:
+**MANDATORY:** Ensure research context exists before creating the ADR. The process will:
 
-1. Check for existing research on the decision topic
-2. If no research found: **automatically read and execute** the complete research workflow from `/research`
+1. Check for existing research on the decision topic in `.code-captain/research/`
+2. If no research found: conduct targeted inline research as part of Step 0
 3. Only proceed with ADR creation after research is completed and documented
 
-### Step 0: Check for Existing Research and Auto-Execute if Missing
+### Step 0: Research Verification & Targeted Research
 
-**Objective:** Ensure comprehensive research exists before creating ADR - automatically execute research if missing
+**Objective:** Ensure sufficient research context exists before creating the ADR
 
 **Actions:**
 
 1. **Check for existing research:**
-
    - Use `search` to look for related research in `.code-captain/research/` directory
-   - Search for research documents that might relate to the architectural decision
+   - Search for research documents that relate to the architectural decision topic
    - Use `codebase` to explore the research directory structure
 
-2. **Automatic research execution if missing:**
-
-   ```
-   If no relevant research found:
-   "No existing research found for this architectural decision.
-
-   Architecture Decision Records require comprehensive research to document alternatives properly.
-
-   AUTOMATICALLY EXECUTING RESEARCH WORKFLOW FIRST...
+2. **If relevant research exists:**
+   - Load and summarize key findings
+   - Identify any gaps that need additional investigation for the ADR
+   - Proceed to Step 1 with research context loaded
 
-   Reading research workflow and executing complete research process..."
-   ```
+3. **If NO relevant research exists — conduct targeted ADR research inline:**
 
-3. **Execute research workflow automatically:**
+   Perform focused research specific to the architectural decision (do NOT attempt to invoke the `/research` command as a sub-prompt):
 
-   - **IMMEDIATELY** execute the complete `/research` command
-   - **CREATE** research document in `.code-captain/research/{date}-{topic}-research.md`
-   - **ONLY CONTINUE** with ADR creation after research is completed
+   a. **Define the decision scope** — What specific architectural question needs answering?
+   b. **Gather alternatives** — Use `fetch` to research 2-4 approaches:
+      - "[technology/pattern] architectural approaches"
+      - "[option A] vs [option B] comparison"
+      - "[technology] production experience case study"
+   c. **Evaluate against project context** — Use `codebase` to understand how each alternative fits the current architecture
+   d. **Document findings** — Get the current date using `npx @devobsessed/code-captain date`, then create a research document in `.code-captain/research/[DATE]-[topic]-research.md` with key findings, pros/cons, and sources
 
-4. **Handle research workflow:**
-   - If no research found: **AUTOMATICALLY execute complete research workflow first**
-   - If existing research found: Load and reference it throughout the ADR process
-   - If research is incomplete: Execute additional research before continuing
+4. **Progress checkpoint:**
+   Before proceeding to Step 1, confirm:
+   - Research document exists and is referenced
+   - At least 2 alternatives have been identified with pros/cons
+   - Project-specific implications have been assessed
 
 **Deliverables:**
 
 - Research availability assessment
-- **Completed research documentation** (auto-executed if missing)
-- Research document ready for ADR reference
+- Research document (loaded from existing or created inline)
+- Summary of key findings ready for ADR reference
 
 ### Step 1: Analyze Decision Context and Current State
 

package/copilot/prompts/create-spec.prompt.md

@@ -11,12 +11,36 @@ Your mission: Turn the user's rough feature idea into a clear work specification
 
 ### Phase 1: Contract Establishment (No File Creation)
 
+#### Step 1.0: Pre-flight Check
+
+Before starting, verify these foundational files exist in `.code-captain/docs/`:
+
+- `tech-stack.md`
+- `code-style.md`
+- `objective.md`
+
+If **ANY** of these files are missing, inform the user before proceeding:
+
+```text
+I notice this project hasn't been fully initialized — the foundational docs
+(tech-stack, code-style, objective) are missing from .code-captain/docs/.
+Running /initialize first will produce better specification results because
+I'll have your project's architecture, conventions, and patterns as context.
+
+Would you like to:
+1. Switch to /initialize now (recommended)
+2. Continue with /create-spec without the foundational context
+```
+
+If the user chooses option 2, proceed but note that pattern detection will rely entirely on live codebase scanning rather than pre-analyzed documentation.
+
 #### Step 1.1: Initial Context Scan
 
 - Scan existing `.code-captain/specs/` for related specifications
 - Analyze current codebase architecture and patterns using `codebase`
-- Load project context files (`tech-stack.md`, `code-style.md`, `objective.md`)
-- **Output:** Context summary (no files created yet)
+- Load project context files if they exist (`tech-stack.md`, `code-style.md`, `objective.md`)
+- **Identify existing codebase patterns** — Catalog naming conventions, project structure patterns, architectural layers (e.g., repository/service/controller), dependency injection patterns, and any established conventions. These become automatic constraints for the specification.
+- **Output:** Context summary including detected patterns (no files created yet)
 
 #### Step 1.2: Gap Analysis & Silent Enumeration
 
@@ -85,7 +109,7 @@ When confident, present a contract proposal with any concerns surfaced:
 
 **Format:**
 
-```
+```text
 ## Specification Contract
 
 **Deliverable:** [One clear sentence describing what will be built]
@@ -104,6 +128,11 @@ When confident, present a contract proposal with any concerns surfaced:
 - [Specific concern about feasibility, performance, or architecture]
 - [Suggested alternative or mitigation approach]
 
+**Existing Patterns to Follow:**
+- [Patterns detected from codebase scan or code-style.md — e.g., repository pattern, service layer, naming conventions]
+- [Architectural layers and their relationships]
+- [Any relevant conventions that new code must adhere to]
+
 **Recommendations:**
 - [Suggestions for improving the approach based on codebase analysis]
 - [Ways to reduce risk or complexity]
@@ -132,7 +161,7 @@ This returns the current date in `YYYY-MM-DD` format for folder naming:
 
 **Generated folder (using determined date):**
 
-```
+```text
 .code-captain/specs/[DATE]-{feature-name}/
 ├── spec.md                    # Main specification (from contract)
 ├── spec-lite.md              # Condensed version for AI context
@@ -273,7 +302,7 @@ Each user story gets its own file for better organization. Keep implementation t
 
 Present complete package with file references:
 
-```
+```text
 Specification package created successfully!
 
 .code-captain/specs/[DATE]-feature-name/
@@ -302,9 +331,19 @@ Please read through the files and let me know:
 - Are the user stories appropriately sized (5-7 tasks each)?
 - Should any stories be split further or combined?
 
-Once you're satisfied with the specification, I can help you start implementation with the first story, or we can make any needed adjustments.
+Once you're satisfied with the specification, you can start implementation using /execute-task, or we can make any needed adjustments.
 ```
 
+## CRITICAL: Command Boundary — STOP HERE
+
+**This command ENDS after presenting the spec package review above.**
+
+- **DO NOT** proceed to implement any code from the stories.
+- **DO NOT** begin executing tasks, writing tests, or making code changes.
+- **DO NOT** offer to "get started on the first story" and then begin coding.
+- Your ONLY job is to create the specification documents. Implementation is handled by the `/execute-task` command.
+- After presenting the final review, **STOP and wait for the user's response.**
+
 ## Tool Integration
 
 **Primary tools:**
@@ -323,7 +362,7 @@ Once you're satisfied with the specification, I can help you start implementatio
 
 ## Example of expected interaction
 
-```
+```text
 Developer: /create-spec "real-time multiplayer chat with blockchain integration"
 
 Agent: I'm ready to help you create a comprehensive specification.

package/copilot/prompts/edit-spec.prompt.md

@@ -141,6 +141,9 @@ Options:
 #### Step 2.1: Create Backup & Change Documentation
 
 **Backup Process:**
+
+**IMPORTANT:** Use repo-root-relative paths for all backup operations. If working in a monorepo or solution with subdirectories, ensure all `.code-captain/` paths reference the repository root, not the current working directory. Use `editFiles` for file creation rather than `runCommands` with `cp` when possible to avoid cwd drift.
+
 1. **CREATE** backup folder: `.code-captain/specs/[spec-folder]/backups/`
 2. **COPY** all current files to `backups/[timestamp]/`
 3. **CREATE** change log entry in `CHANGELOG.md` within spec folder

package/copilot/prompts/execute-task.prompt.md

@@ -44,6 +44,7 @@ Create `.code-captain/current-task-progress.md` to track the execution process:
 ## Progress Steps:
 - [x] Task discovery and selection
 - [ ] Context gathering from specs and codebase
+- [ ] Project structure & infrastructure verification
 - [ ] Subtask execution in TDD order
 - [ ] Test verification (100% pass rate required)
 - [ ] Task completion and status update
@@ -51,6 +52,12 @@ Create `.code-captain/current-task-progress.md` to track the execution process:
 ## Current Step: Task Discovery
 ```
 
+**Progress tracker update triggers:**
+- Update after completing each numbered sub-task
+- Update when encountering unexpected prerequisite work (e.g., "Added test framework setup — not in original task list")
+- Record test run results with pass/fail counts after each test execution
+- Update the "Current Step" indicator as you move through phases
+
 ### Step 2: Context Gathering & Analysis
 
 **Load specification context:**
@@ -70,6 +77,51 @@ Use `codebase` and `search` to understand:
 - Integration points for new features
 - Testing frameworks and conventions
 
+### Step 2.5: Project Structure & Infrastructure Verification
+
+Before writing any code or tests, verify the project environment.
+
+**Check existing project documentation:**
+
+- If `.code-captain/docs/tech-stack.md` exists and contains project topology and test infrastructure status, use it rather than re-detecting from scratch
+- Only perform fresh detection if `tech-stack.md` is missing or stale
+
+**Detect project structure:**
+
+1. Search for `*.sln` files at the repository root
+2. If a solution file exists:
+   - Identify project subdirectories (client, server, shared, etc.)
+   - Determine which subdirectory contains the implementation target
+   - Note the repo root path — all `.code-captain/` references are relative to root
+3. If no solution file exists, treat the workspace root as the project root
+
+**Verify test infrastructure:**
+
+1. Check `package.json` (in the target directory) for a `test` script and test-related `devDependencies`
+2. If NO test framework exists:
+   - Select a test runner aligned with the project's build tool (e.g., Vitest for Vite, Jest for Webpack/CRA)
+   - Install minimum required packages (test runner, DOM environment, assertion matchers)
+   - Configure the test runner in the project's existing config file
+   - Create a setup file if needed (e.g., for jest-dom matchers)
+   - Add a `test` script to `package.json`
+   - Run a trivial smoke test to confirm the framework works before writing real tests
+3. If a test framework exists, verify it runs successfully with any existing tests
+4. Document test infrastructure additions in the progress tracker
+
+**Select test strategies (based on project stack):**
+
+For JavaScript/TypeScript projects:
+- **Component behavior tests**: Use the project's testing library (e.g., React Testing Library with `render`, `screen`, `fireEvent`) for rendered output and interactions
+- **Static file content tests** (CSS variables, import assertions, file structure): Use Node.js `fs.readFileSync` to read source files as text — do NOT use `fetch()` which is unavailable or incomplete in test DOM environments (jsdom does not support `fetch` for `file://` URLs)
+- **Integration tests**: Use the test runner's DOM environment for full component mounting
+
+For .NET projects:
+- Use the project's existing test framework (xUnit, NUnit, MSTest)
+- Run tests with `dotnet test` (already non-interactive)
+
+For other stacks:
+- Align test strategy with the framework and conventions detected in `tech-stack.md` or discovered during infrastructure verification
+
 ### Step 3: Story & Task Analysis
 
 Parse selected story structure and validate TDD approach within story using file-based progress tracking instead of todo_write.
@@ -84,7 +136,16 @@ Execute story tasks in sequential order with file-based tracking:
 - Write comprehensive test cases for the entire feature
 - Include unit tests, integration tests, and edge cases
 - Cover happy path, error conditions, and boundary cases
-- Ensure tests fail appropriately (red phase)
+- Use the appropriate test strategy from Step 2.5 (component tests vs static file tests vs integration tests)
+
+**Red Phase Verification (mandatory before proceeding to green phase):**
+1. Run the test suite after writing tests
+2. Confirm tests produce **assertion failures** (e.g., "expected X but received Y") — not runtime errors or crashes
+3. If tests error/crash instead of failing (e.g., `TypeError`, `fetch failed`, `Module not found`):
+   - This means the test infrastructure or test approach is broken, not the feature code
+   - Fix the test setup or rewrite the test approach
+   - Re-run until tests fail cleanly with assertion messages
+4. Only proceed to the green phase once all tests fail with clear assertion errors
 
 #### Tasks 2-N: Implementation (Green Phase)
 
@@ -108,6 +169,17 @@ For each implementation task within the story:
 
 **STORY CANNOT BE MARKED COMPLETE WITH ANY FAILING TESTS**
 
+### CRITICAL: One Story at a Time
+
+**Execute ONLY the single selected story per invocation of this command.**
+
+- After completing Step 4 (all tasks within the story) and verifying tests pass, proceed to Step 5.
+- After Step 5, **STOP execution completely.**
+- **DO NOT** automatically begin the next story.
+- **DO NOT** ask "shall I continue with story 2?" and then start coding before the user responds.
+- Present the completion summary and **wait for the user** to explicitly request the next story.
+- The user must invoke `/execute-task` again or explicitly ask to continue with the next story.
+
 ### Step 5: Story Completion & Status Updates
 
 Update story file status and progress tracking files with completion details, ensuring all tests pass before marking complete.
@@ -118,12 +190,39 @@ Update story file status and progress tracking files with completion details, en
 - `codebase` - Understanding existing architecture and patterns
 - `search` - Finding related code and patterns
 - `editFiles` - Implementing code changes
-- `runCommands` - Executing build processes
+- `runCommands` - Executing build processes (follow Terminal Command Standards from system instructions)
 - `runTests` - Running test suites
 - `findTestFiles` - Locating test files
 - `testFailure` - Analyzing test failures
 
+**Terminal discipline (see system instructions for full standards):**
+- Always use non-interactive, single-run flags for test runners (e.g., `vitest run`, `jest --ci`)
+- Never start dev servers or watch-mode processes — they block the chat session
+- When running commands in subdirectories, use `cd <subdir> && <command>` to preserve cwd
+- Verify `npm test` script contents before using it — scripts may invoke watch mode
+
 **Progress tracking:**
 - File-based progress tracking in `.code-captain/current-task-progress.md`
 - Story status updates in specification files
-- Test execution results documentation
+- Test execution results documentation with pass/fail counts
+
+## CRITICAL: Command Boundary — STOP After Story Completion
+
+After completing a story and updating status files, present a summary in this format:
+
+```
+Story [N]: [Title] — COMPLETED
+
+Results:
+- Tests: [X] passed, [Y] failed
+- Tasks completed: [N/N]
+- Acceptance criteria: [all met / details]
+
+Updated files:
+- [list of modified/created files]
+
+Next available story: Story [N+1]: [Title]
+To continue, invoke /execute-task again or ask me to proceed with the next story.
+```
+
+**STOP here. Do NOT begin the next story automatically.**

package/copilot/prompts/initialize.prompt.md

@@ -9,7 +9,7 @@ You MUST follow these instructions exactly. Do NOT describe this process — exe
 
 Your mission: Analyze the current project and set up the technical foundation. Detect whether this is a greenfield (new) or brownfield (existing) project, scan the codebase, and generate foundational documentation.
 
-### Step 1: Project Type Detection
+### Step 1: Project Type & Structure Detection
 
 **Scan for existing code:**
 - Check for common files indicating existing project (package.json, pom.xml, etc.)
@@ -17,6 +17,16 @@ Your mission: Analyze the current project and set up the technical foundation. D
 - Identify project structure patterns
 - Determine if greenfield (new) or brownfield (existing) project
 
+**Detect project topology:**
+- Search for `*.sln` files at the repository root (indicates .NET solution / monorepo)
+- Search for multiple `package.json` files (indicates JavaScript/TypeScript monorepo)
+- Check for workspace configurations (`pnpm-workspace.yaml`, `lerna.json`, `nx.json`)
+- If a solution or monorepo is detected:
+  - Map all sub-projects and their locations relative to the repo root
+  - Identify which sub-projects are frontend, backend, shared libraries, etc.
+  - Note each sub-project's independent tooling (build tool, test runner, package manager)
+  - Document the topology in Step 3 (tech-stack.md)
+
 ### Step 2: Project Analysis
 
 **For Brownfield Projects:**
@@ -25,6 +35,15 @@ Your mission: Analyze the current project and set up the technical foundation. D
 - Infer project purpose and goals
 - Generate comprehensive documentation
 
+**Test infrastructure inventory (all project types):**
+- For each sub-project (or the root project if not a monorepo):
+  - Check `package.json` for `test` script and test-related `devDependencies`
+  - Identify the test runner (Vitest, Jest, xUnit, NUnit, MSTest, pytest, etc.)
+  - Note the test configuration file location (vite.config, jest.config, etc.)
+  - Check if a test setup file exists (test-setup.js, setupTests.ts, etc.)
+  - Record whether tests currently pass, fail, or if no test infrastructure exists
+- Document findings in `tech-stack.md` so downstream commands (especially `execute-task`) have this context
+
 **For Greenfield Projects:**
 - Guide through strategic project setup questions
 - Recommend technology stack based on requirements
@@ -34,7 +53,10 @@ Your mission: Analyze the current project and set up the technical foundation. D
 
 Generate foundational documents in `.code-captain/docs/`:
 
-- **tech-stack.md** - Complete technology inventory and analysis
+- **tech-stack.md** - Complete technology inventory and analysis. Must include:
+  - Project topology (single project, monorepo, or .NET solution with sub-projects)
+  - For each sub-project: build tool, test runner (or "none"), test configuration location
+  - Test infrastructure status: "ready" (tests exist and pass), "configured" (framework installed but no tests), or "missing" (no test framework)
 - **code-style.md** - Observed patterns and coding conventions
 - **objective.md** - Inferred or defined project purpose and goals
 - **architecture.md** - System architecture overview and decisions
@@ -57,6 +79,13 @@ Provide clear guidance on next steps, typically:
 - `findTestFiles` - Locating test files and patterns
 - `problems` - Identifying code issues
 
+**Terminal discipline:** Follow Terminal Command Standards from system instructions. When detecting build tools and dependencies, use non-blocking commands (e.g., check file existence rather than running full builds). In monorepos, use `cd <subdir> && <command>` to avoid cwd drift.
+
 **Documentation organization:**
 - Progress documented in `.code-captain/initialization-progress.md`
 - Results organized in `.code-captain/docs/` folder
+
+**Progress tracker updates:**
+- Update `.code-captain/initialization-progress.md` after completing each step
+- Record unexpected findings (e.g., "No test framework found in client project")
+- Document project topology discoveries as they occur

package/copilot/prompts/status.prompt.md

@@ -28,6 +28,8 @@ Your mission: Provide the developer with a comprehensive status report. Analyze
 **Code Captain Integration:**
 - Scan `.code-captain/specs/` for active specifications
 - Parse current task progress from most recent spec's user-stories/
+- Check `.code-captain/current-task-progress.md` for in-flight execution state
+- Check `.code-captain/initialization-progress.md` for initialization status
 - Identify completed vs pending tasks
 - Determine current user story context
 
@@ -38,16 +40,26 @@ Your mission: Provide the developer with a comprehensive status report. Analyze
 
 ### Step 3: Project Health Check
 
-**Basic Viability:**
-- Can the project build/compile? (language-specific checks)
-- Are core services startable?
-- Any obvious configuration issues?
-- Dependencies status (package.json, requirements.txt, etc.)
+**IMPORTANT: Use passive, non-blocking checks only. Do NOT run builds, start services, or execute long-running commands.**
+
+**Basic Viability (file-based heuristics):**
+- Check for build artifacts (e.g., `dist/`, `build/`, `bin/`, `obj/`) — presence suggests a recent successful build
+- Check lock file freshness (`package-lock.json`, `yarn.lock`, `pnpm-lock.yaml`) — staleness may indicate missing dependencies
+- Check for TypeScript errors via `problems` tool if available
+- Verify key configuration files exist (`.env`, `appsettings.json`, etc.)
+- Check `node_modules/` existence — missing suggests `npm install` is needed
+- For .NET projects: check for `*.csproj` build errors via `problems` tool, not `dotnet build`
+
+**Do NOT run these commands during status checks:**
+- `npm run build`, `dotnet build`, or any full compilation
+- `npm start`, `dotnet run`, or any dev server startup
+- `npm test` or `dotnet test` — report test infrastructure status from file inspection only
 
 **Immediate Blockers:**
 - Merge conflicts that need resolution
-- Missing environment variables or config files
-- Failed builds or critical errors
+- Missing environment variables or config files (check for `.env.example` without corresponding `.env`)
+- Missing `node_modules/` or other dependency directories
+- Stale lock files suggesting dependency drift
 
 ### Step 4: Output the Status Report
 
@@ -97,7 +109,7 @@ QUICK COMMANDS
 **Primary tools:**
 - `codebase` - Analyzing project structure and Code Captain specs
 - `search` - Finding active specifications and related documentation
-- `runCommands` - Git commands and system health checks
+- `runCommands` - Git commands only (follow Terminal Command Standards from system instructions — no builds, no dev servers)
 - `problems` - Identifying project health issues and conflicts
 - `changes` - Tracking recent modifications and activity
 

package/cursor/commands/create-spec.md

@@ -12,12 +12,36 @@ Generate comprehensive feature specifications using a contract-first approach th
 
 > Your goal is to turn my rough feature idea into a very clear work specification. You will deliver the complete spec package only after we both agree on the requirements contract. **Important: Challenge ideas that don't make technical or business sense - it's better to surface concerns early than build the wrong thing.**
 
+#### Step 1.0: Pre-flight Check
+
+Before starting, verify these foundational files exist in `.code-captain/docs/`:
+
+- `tech-stack.md`
+- `code-style.md`
+- `objective.md`
+
+If **ANY** of these files are missing, inform the user before proceeding:
+
+```text
+I notice this project hasn't been fully initialized — the foundational docs
+(tech-stack, code-style, objective) are missing from .code-captain/docs/.
+Running /initialize first will produce better specification results because
+I'll have your project's architecture, conventions, and patterns as context.
+
+Would you like to:
+1. Switch to /initialize now (recommended)
+2. Continue with /create-spec without the foundational context
+```
+
+If the user chooses option 2, proceed but note that pattern detection will rely entirely on live codebase scanning rather than pre-analyzed documentation.
+
 #### Step 1.1: Initial Context Scan
 
 - Scan existing `.code-captain/specs/` for related specifications
 - Analyze current codebase architecture and patterns using `codebase_search`
-- Load project context files (`tech-stack.md`, `code-style.md`, `objective.md`)
-- **Output:** Context summary (no files created yet)
+- Load project context files if they exist (`tech-stack.md`, `code-style.md`, `objective.md`)
+- **Identify existing codebase patterns** — Catalog naming conventions, project structure patterns, architectural layers (e.g., repository/service/controller), dependency injection patterns, and any established conventions. These become automatic constraints for the specification.
+- **Output:** Context summary including detected patterns (no files created yet)
 
 #### Step 1.2: Gap Analysis & Silent Enumeration
 
@@ -86,7 +110,7 @@ When confident, present a contract proposal with any concerns surfaced:
 
 **Format:**
 
-```
+```text
 ## Specification Contract
 
 **Deliverable:** [One clear sentence describing what will be built]
@@ -105,6 +129,11 @@ When confident, present a contract proposal with any concerns surfaced:
 - [Specific concern about feasibility, performance, or architecture]
 - [Suggested alternative or mitigation approach]
 
+**Existing Patterns to Follow:**
+- [Patterns detected from codebase scan or code-style.md — e.g., repository pattern, service layer, naming conventions]
+- [Architectural layers and their relationships]
+- [Any relevant conventions that new code must adhere to]
+
 **💡 Recommendations:**
 - [Suggestions for improving the approach based on codebase analysis]
 - [Ways to reduce risk or complexity]
@@ -124,7 +153,7 @@ Options:
 
 #### Step 2.1: Initialize Tracking
 
-```bash
+```text
 # Use todo_write to track creation process
 1. Get current date and create spec folder structure
 2. Generate core specification document
@@ -145,7 +174,7 @@ This returns the current date in `YYYY-MM-DD` format for folder naming:
 
 **Generated folder (using determined date):**
 
-```
+```text
 .code-captain/specs/[DATE]-{feature-name}/
 ├── spec.md                    # Main specification (from contract)
 ├── spec-lite.md              # Condensed version for AI context
@@ -311,7 +340,7 @@ This returns the current date in `YYYY-MM-DD` format for folder naming:
 
 Present complete package with file references:
 
-```
+```text
 ✅ Specification package created successfully!
 
 📁 .code-captain/specs/[DATE]-feature-name/
@@ -347,9 +376,19 @@ The user-stories folder structure allows you to:
 - Assign different stories to different team members
 - Keep task lists manageable and actionable
 
-Once you're satisfied with the specification, I can help you start implementation with the first story, or we can make any needed adjustments.
+Once you're satisfied with the specification, you can start implementation using /execute-task, or we can make any needed adjustments.
 ```
 
+## CRITICAL: Command Boundary — STOP HERE
+
+**This command ENDS after presenting the spec package review above.**
+
+- **DO NOT** proceed to implement any code from the stories.
+- **DO NOT** begin executing tasks, writing tests, or making code changes.
+- **DO NOT** offer to "get started on the first story" and then begin coding.
+- Your ONLY job is to create the specification documents. Implementation is handled by the `/execute-task` command.
+- After presenting the final review, **STOP and wait for the user's response.**
+
 ## Key Improvements Over Original
 
 ### 1. Contract-First Approach
@@ -379,7 +418,7 @@ Once you're satisfied with the specification, I can help you start implementatio
 
 ## Example Usage Flow
 
-```
+```text
 Developer: /create-spec "real-time multiplayer chat with blockchain integration"
 
 Agent: I'm ready to help you create a comprehensive specification.

package/cursor/commands/execute-task.md

@@ -285,6 +285,17 @@ Use available testing tools to verify:
 4. Repeat until NO tests fail
 5. Only then mark story as complete
 
+### CRITICAL: One Story at a Time
+
+**Execute ONLY the single selected story per invocation of this command.**
+
+- After completing Step 6 (test validation) and verifying tests pass, proceed to Step 7.
+- After Step 7, **STOP execution completely.**
+- **DO NOT** automatically begin the next story.
+- **DO NOT** ask "shall I continue with story 2?" and then start coding before the user responds.
+- Present the completion summary and **wait for the user** to explicitly request the next story.
+- The user must invoke `/execute-task` again or explicitly ask to continue with the next story.
+
 ### Step 7: Story Completion & Status Updates
 
 **Update story file status:**
@@ -367,9 +378,11 @@ Next available stories:
 - Story 2: Password Reset (4 tasks) - Not Started
 - Story 3: Profile Management (6 tasks) - Not Started
 
-Would you like to proceed with the next story?
+To continue, invoke /execute-task again or ask me to proceed with the next story.
 ```
 
+**STOP here. Do NOT begin the next story automatically.**
+
 **If ANY tests fail, present this instead:**
 
 ```

package/manifest.json

@@ -1,14 +1,14 @@
 {
-  "version": "0.2.2",
-  "timestamp": "2026-02-11T22:53:25.745Z",
-  "commit": "c74b5fbcf9c1e4eed4851c3d7ed3e065c81d19d0",
+  "version": "0.3.0",
+  "timestamp": "2026-02-12T13:09:10.578Z",
+  "commit": "a18e9dc145c3990823850611b321d0713e63d657",
   "description": "Code Captain file manifest for change detection",
   "files": {
     "cursor/cc.mdc": {
       "hash": "sha256:92bf482f44684af5072358908dfece0247470d14d7bdfd15d7ee83a9127ff199",
       "size": 4800,
       "lastModified": "2025-11-25T16:41:04.604Z",
-      "version": "0.2.2",
+      "version": "0.3.0",
       "component": "rules",
       "description": "You are **Code Captain** - a methodical AI development partner who executes comprehensive software w..."
     },
@@ -16,7 +16,7 @@
       "hash": "sha256:5a80261ed75b56c6eb58b7e11a951f5ac1cdf184290582bdd8210bea1bb820b2",
       "size": 15818,
       "lastModified": "2025-11-25T16:41:04.605Z",
-      "version": "0.2.2",
+      "version": "0.3.0",
       "component": "commands",
       "description": "Create comprehensive Architecture Decision Records (ADRs) that systematically document architectural..."
     },
@@ -24,7 +24,7 @@
       "hash": "sha256:f7305a4584b2f291fc494bee035c20d7dd48dc2f6ea913982ee96773e24e8499",
       "size": 17742,
       "lastModified": "2025-11-25T16:41:04.605Z",
-      "version": "0.2.2",
+      "version": "0.3.0",
       "component": "commands",
       "description": "Generate comprehensive feature specifications using a contract-first approach that ensures complete ..."
     },
@@ -32,7 +32,7 @@
       "hash": "sha256:95836eba17d903953a4c4209a69c33eb6ad19f276f472d66c13887a8094868e2",
       "size": 16803,
       "lastModified": "2025-11-25T16:41:04.605Z",
-      "version": "0.2.2",
+      "version": "0.3.0",
       "component": "commands",
       "description": "Modify existing feature specifications using a contract-first approach that ensures complete alignme..."
     },
@@ -40,7 +40,7 @@
       "hash": "sha256:01323eaf32a4b44cc4c2abdaccd728245448070235a8d623751449e8daf23871",
       "size": 16496,
       "lastModified": "2025-11-25T16:41:04.605Z",
-      "version": "0.2.2",
+      "version": "0.3.0",
       "component": "commands",
       "description": "Execute a specific task and its sub-tasks systematically following a Test-Driven Development (TDD) w..."
     },
@@ -48,7 +48,7 @@
       "hash": "sha256:e44b9353ca3fa1f332af52f1e2b6148e152bb12a16e52b81cc9f5794d453a9e2",
       "size": 6974,
       "lastModified": "2025-11-25T16:41:04.605Z",
-      "version": "0.2.2",
+      "version": "0.3.0",
       "component": "commands",
       "description": "The `explain-code` command provides comprehensive, AI-powered explanations of code segments, functio..."
     },
@@ -56,7 +56,7 @@
       "hash": "sha256:a519ecaacb02097b1d12a43a34ac3498a6bf9b47ecc6cb6621dd84b3d4970a10",
       "size": 11267,
       "lastModified": "2025-11-25T16:41:04.605Z",
-      "version": "0.2.2",
+      "version": "0.3.0",
       "component": "commands",
       "description": "Set up technical foundation and development infrastructure by detecting if this is a greenfield (new..."
     },
@@ -64,7 +64,7 @@
       "hash": "sha256:3b3d9be4e4b66ca4bd461b2dee8681217fd3c6681dced4736e6d85e793efef3e",
       "size": 14341,
       "lastModified": "2025-11-25T16:41:04.606Z",
-      "version": "0.2.2",
+      "version": "0.3.0",
       "component": "commands",
       "description": "A meta command that creates new Code Captain commands following established patterns and conventions..."
     },
@@ -72,7 +72,7 @@
       "hash": "sha256:90a69bc3334a69af98aa0814e7a00e1e2c4ce4cd0abf32b04f3c577f9437f221",
       "size": 16455,
       "lastModified": "2025-11-25T16:41:04.606Z",
-      "version": "0.2.2",
+      "version": "0.3.0",
       "component": "commands",
       "description": "Generate comprehensive product planning documentation using a contract-first approach that establish..."
     },
@@ -80,7 +80,7 @@
       "hash": "sha256:6def0906545267f6fe14f1d920baa8cce0fdb27f3bae45c2ab9b22e3e6464e0e",
       "size": 8595,
       "lastModified": "2025-11-25T16:41:04.606Z",
-      "version": "0.2.2",
+      "version": "0.3.0",
       "component": "commands",
       "description": "Conduct systematic research on a topic using structured phases that build upon each other, creating ..."
     },
@@ -88,7 +88,7 @@
       "hash": "sha256:48ea3bd849cdfb566778f6d84090878c287cee3e07dd4ec997bdc51fcca40ea4",
       "size": 12793,
       "lastModified": "2025-11-25T16:41:04.606Z",
-      "version": "0.2.2",
+      "version": "0.3.0",
       "component": "commands",
       "description": "A command that provides developers with a comprehensive status report when starting work or switchin..."
     },
@@ -96,7 +96,7 @@
       "hash": "sha256:9faa9403fbd24b992bdd3c6cff204a6c867fb4068a79188ec7cbe5662daf1e4d",
       "size": 8270,
       "lastModified": "2025-11-25T16:41:04.606Z",
-      "version": "0.2.2",
+      "version": "0.3.0",
       "component": "commands",
       "description": "A deck-cleaning agent that makes one small, focused improvement to the codebase, following the \"Boy ..."
     },
@@ -104,15 +104,15 @@
       "hash": "sha256:727c8ae467010da039c41d013c2557d689bfca16f8a93e6b8744c89fa66e27ba",
       "size": 2177,
       "lastModified": "2025-11-25T16:41:04.606Z",
-      "version": "0.2.2",
+      "version": "0.3.0",
       "component": "docs",
       "description": "Global development guidelines for Agent OS projects."
     },
     "copilot/copilot-instructions.md": {
-      "hash": "sha256:9264535377631fad4c858b539cfe010923819cd2f4398126d95870aadef3b96a",
-      "size": 3863,
-      "lastModified": "2026-02-11T22:17:25.560Z",
-      "version": "0.2.2",
+      "hash": "sha256:0f11ce5c0f1ba589f59741027ed6daee95a2d73623d4219c42919125060a801c",
+      "size": 6003,
+      "lastModified": "2026-02-12T12:44:12.842Z",
+      "version": "0.3.0",
       "component": "instructions",
       "description": "You are **Code Captain** - a methodical AI development partner who executes comprehensive software w..."
     },
@@ -120,15 +120,15 @@
       "hash": "sha256:98abb65bb7e48283c8f84a8e679d5bc7935455f2142d6d28465fc59ddd77bbf9",
       "size": 2639,
       "lastModified": "2026-02-11T22:17:25.559Z",
-      "version": "0.2.2",
+      "version": "0.3.0",
       "component": "agents",
       "description": "Code Captain - AI Development Partner"
     },
     "copilot/prompts/create-adr.prompt.md": {
-      "hash": "sha256:d96a955d9e589f1c7d88853eac6e42d7c079eae66e2d2153082ac75c10c64073",
-      "size": 11775,
-      "lastModified": "2026-02-11T22:17:25.560Z",
-      "version": "0.2.2",
+      "hash": "sha256:98398b6f0869d4eb84f08760cf38b6553d107714acc58e392a975d263dae3f44",
+      "size": 12092,
+      "lastModified": "2026-02-12T12:48:34.927Z",
+      "version": "0.3.0",
       "component": "prompts",
       "description": "Create Architecture Decision Records with research and analysis"
     },
@@ -136,23 +136,23 @@
       "hash": "sha256:f30bf21f2a9df38c85a28ad530a52a363b883ea912c4eda492efd6d2dd1d9b02",
       "size": 13846,
       "lastModified": "2026-02-11T22:17:25.560Z",
-      "version": "0.2.2",
+      "version": "0.3.0",
       "component": "prompts",
       "description": "Generate feature specifications using a contract-first approach"
     },
     "copilot/prompts/edit-spec.prompt.md": {
-      "hash": "sha256:50c533454e73dbfcc2db0eaef77bfa201a472b467760610a7a4002dee572419f",
-      "size": 9193,
-      "lastModified": "2026-02-11T22:17:25.560Z",
-      "version": "0.2.2",
+      "hash": "sha256:47b4c636620083d4b5e113afafc358dc1aa5015ca55a6d414ff62543fc53f026",
+      "size": 9528,
+      "lastModified": "2026-02-12T12:46:48.988Z",
+      "version": "0.3.0",
       "component": "prompts",
       "description": "Modify existing feature specifications with change tracking"
     },
     "copilot/prompts/execute-task.prompt.md": {
-      "hash": "sha256:a7b847a5ad23bd240481c0c1f4d416404654f748346448ba9c1d48c71b69a3cd",
-      "size": 4605,
-      "lastModified": "2026-02-11T22:17:25.560Z",
-      "version": "0.2.2",
+      "hash": "sha256:729171a3564b322e46920e8e7b379542bd52c7d0b2d78594e78758b770418791",
+      "size": 8726,
+      "lastModified": "2026-02-12T12:48:51.235Z",
+      "version": "0.3.0",
       "component": "prompts",
       "description": "Execute implementation tasks using TDD from specifications"
     },
@@ -160,15 +160,15 @@
       "hash": "sha256:63a083e461fd536f9232ae9051d97b83cb0dedb956353d63d41fce10a5c73ec5",
       "size": 4031,
       "lastModified": "2026-02-11T22:17:25.560Z",
-      "version": "0.2.2",
+      "version": "0.3.0",
       "component": "prompts",
       "description": "Generate comprehensive code explanations with diagrams"
     },
     "copilot/prompts/initialize.prompt.md": {
-      "hash": "sha256:a07e22de68c6d8adea0e428b546056cac45c17424ebe5d841e02b25707106883",
-      "size": 2328,
-      "lastModified": "2026-02-11T22:17:25.561Z",
-      "version": "0.2.2",
+      "hash": "sha256:b9cf96bf153c77eb759cca6074dec0cb49c0700c7cde96743e8af7d71b8d72c0",
+      "size": 4450,
+      "lastModified": "2026-02-12T12:45:46.356Z",
+      "version": "0.3.0",
       "component": "prompts",
       "description": "Analyze and set up project foundation with documentation"
     },
@@ -176,7 +176,7 @@
       "hash": "sha256:ed321a43dcd7276a65752a97573acad956cd8904667544d795b7441d643a71f0",
       "size": 5516,
       "lastModified": "2026-02-11T22:17:25.561Z",
-      "version": "0.2.2",
+      "version": "0.3.0",
       "component": "prompts",
       "description": "Create new Code Captain commands following established patterns"
     },
@@ -184,7 +184,7 @@
       "hash": "sha256:e7614e39e7b1d04f6cb8952188a9539422a26d2d2da754799f6424e167e3ea28",
       "size": 6854,
       "lastModified": "2026-02-11T22:17:25.561Z",
-      "version": "0.2.2",
+      "version": "0.3.0",
       "component": "prompts",
       "description": "Transform product ideas into comprehensive plans"
     },
@@ -192,15 +192,15 @@
       "hash": "sha256:33702a0fd7b87059f7163e09d66b305cf9a06531d4133ab9c999a9f3d9795f56",
       "size": 5333,
       "lastModified": "2026-02-11T22:17:25.561Z",
-      "version": "0.2.2",
+      "version": "0.3.0",
       "component": "prompts",
       "description": "Conduct systematic research using structured phases"
     },
     "copilot/prompts/status.prompt.md": {
-      "hash": "sha256:9e33640760c5af58498eecdb4dc6f9e97f5b53fadb8a296fb449ba111ada135f",
-      "size": 3734,
-      "lastModified": "2026-02-11T22:17:25.561Z",
-      "version": "0.2.2",
+      "hash": "sha256:a0dc9009a9b031d42c3cff0cf26d289a0269ccc2cfcc36c1b42951caa3f9eba2",
+      "size": 4866,
+      "lastModified": "2026-02-12T12:48:58.243Z",
+      "version": "0.3.0",
       "component": "prompts",
       "description": "Provide comprehensive project status with next actions"
     },
@@ -208,7 +208,7 @@
       "hash": "sha256:79604fde524fd1e7c785ea1d7e84316929e17084c42c9928d1114f127bec0a80",
       "size": 2847,
       "lastModified": "2026-02-11T22:17:25.562Z",
-      "version": "0.2.2",
+      "version": "0.3.0",
       "component": "prompts",
       "description": "Make one focused code improvement following the Boy Scout Rule"
     },
@@ -216,15 +216,15 @@
       "hash": "sha256:727c8ae467010da039c41d013c2557d689bfca16f8a93e6b8744c89fa66e27ba",
       "size": 2177,
       "lastModified": "2025-11-25T16:41:04.601Z",
-      "version": "0.2.2",
+      "version": "0.3.0",
       "component": "docs",
       "description": "Global development guidelines for Agent OS projects."
     },
     "copilot/Directory.Build.props": {
       "hash": "sha256:3a9c06c556e462dd5697d6852bcef712af3ab80581d00cee7f2de412a7abb729",
       "size": 475,
-      "lastModified": "2026-02-11T22:52:22.502Z",
-      "version": "0.2.2",
+      "lastModified": "2026-02-11T23:21:47.573Z",
+      "version": "0.3.0",
       "component": "vs-solution",
       "description": "<!-- Code Captain: Make .github/ Copilot files visible in VS Solution Explorer -->"
     },
@@ -232,7 +232,7 @@
       "hash": "sha256:6d87de22934ab5eecc48a899907dba6c38d2ecc30e96aa871eaf4fe4d500a08f",
       "size": 5832,
       "lastModified": "2025-11-25T16:41:04.600Z",
-      "version": "0.2.2",
+      "version": "0.3.0",
       "component": "agents",
       "description": "Comprehensive AI development partner for coordinating software development workflows. Use proactively for project setup, requirements analysis, feature specifications, architecture decisions, implementation planning, and platform integrations across the entire development lifecycle."
     },
@@ -240,7 +240,7 @@
       "hash": "sha256:ee220ded638b37fe29c519f8b21311b535c871b9d0f276d0cb7a609241bac497",
       "size": 8644,
       "lastModified": "2025-11-25T16:41:04.600Z",
-      "version": "0.2.2",
+      "version": "0.3.0",
       "component": "agents",
       "description": "Specialized agent for generating core specification documents from locked contracts. Creates spec.md and spec-lite.md files with proper structure and formatting."
     },
@@ -248,7 +248,7 @@
       "hash": "sha256:3968ec61d6530c165d594448ad703ddee9fb4ddc84fe6a414c6ed4fcc836c596",
       "size": 11225,
       "lastModified": "2025-11-25T16:41:04.600Z",
-      "version": "0.2.2",
+      "version": "0.3.0",
       "component": "agents",
       "description": "Specialized agent for creating user stories with focused task breakdown. Generates individual story files with 5-7 tasks each, following TDD patterns and ensuring each story delivers standalone user value."
     },
@@ -256,7 +256,7 @@
       "hash": "sha256:22e055c35614ff928c62540eb3459b8841b2f48852d999ab949d35ebc9cdd108",
       "size": 12800,
       "lastModified": "2025-11-25T16:41:04.600Z",
-      "version": "0.2.2",
+      "version": "0.3.0",
       "component": "agents",
       "description": "Specialized agent for generating technical specifications based on requirements. Creates architecture documents, database schemas, API specs, and UI wireframes only when needed, ensuring technical details support user story implementation."
     },
@@ -264,7 +264,7 @@
       "hash": "sha256:5f401313635a46278251df9cba31c0228270b15d6ddd06cf64c72274cee39ea4",
       "size": 25185,
       "lastModified": "2026-02-11T15:17:33.463Z",
-      "version": "0.2.2",
+      "version": "0.3.0",
       "component": "claude-commands",
       "description": "Generate comprehensive feature specifications using a contract-first approach that ensures complete ..."
     },
@@ -272,14 +272,14 @@
       "hash": "sha256:7c94db2c53c3b937377074d1ef272cdc9b026ebb108c68770c4836f476a7abdc",
       "size": 15817,
       "lastModified": "2025-11-25T16:41:04.601Z",
-      "version": "0.2.2",
+      "version": "0.3.0",
       "component": "claude-commands",
       "description": "Set up technical foundation and development infrastructure by detecting if this is a greenfield (new..."
     }
   },
   "changelog": {
-    "0.2.2": {
-      "date": "2026-02-11",
+    "0.3.0": {
+      "date": "2026-02-12",
       "changes": []
     }
   }

package/package.json

@@ -1,11 +1,21 @@
 {
   "name": "@devobsessed/code-captain",
-  "version": "0.2.2",
+  "version": "0.3.2",
   "description": "Unified AI Development Agent System with intelligent change detection",
   "type": "module",
   "bin": {
     "code-captain": "bin/install.js"
   },
+  "scripts": {
+    "manifest": "node scripts/build-manifest.js",
+    "dry-run": "npm publish --dry-run",
+    "publish": "npm publish",
+    "self": "cross-env CC_LOCAL_SOURCE=. node bin/install.js",
+    "test": "vitest run",
+    "test:watch": "vitest --watch",
+    "test:ui": "vitest --ui",
+    "analyze-tokens": "node scripts/analyze-token-counts.js"
+  },
   "keywords": [
     "ai",
     "development",
@@ -53,14 +63,5 @@
   "bugs": {
     "url": "https://github.com/devobsessed/code-captain/issues"
   },
-  "homepage": "https://github.com/devobsessed/code-captain#readme",
-  "scripts": {
-    "manifest": "node scripts/build-manifest.js",
-    "dry-run": "npm publish --dry-run",
-    "self": "cross-env CC_LOCAL_SOURCE=. node bin/install.js",
-    "test": "vitest run",
-    "test:watch": "vitest --watch",
-    "test:ui": "vitest --ui",
-    "analyze-tokens": "node scripts/analyze-token-counts.js"
-  }
-}
+  "homepage": "https://github.com/devobsessed/code-captain#readme"
+}