claude-code-conductor 0.0.1

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,72 @@
+# Claude Code Conductor
+
+> A context-driven wrapper for Claude Code to enforce spec-driven development.
+
+**Claude Code Conductor** is a CLI tool that wraps [Claude Code](https://docs.anthropic.com/claude/docs/claude-code) to provide a structured, context-aware development workflow. It ensures that every session starts with the correct context (`product.md`, `tech-stack.md`, `plan.md`) and enforces a disciplined "Spec -> Plan -> Implement" cycle.
+
+## Features
+
+-   **Context Management:** Automatically loads relevant project documentation into Claude's context.
+-   **Track System:** Manages feature development through "Tracks" (`tracks.md`) with dedicated specs and plans.
+-   **Workflow Enforcement:** Guides users through the proper development lifecycle (Spec, Plan, Red, Green, Refactor).
+-   **Slash Command Integration:** Registers commands like `/conductor:setup`, `/conductor:implement`, and `/conductor:status` directly in Claude Code.
+
+## Installation
+
+```bash
+npm install -g claude-code-conductor
+```
+
+## Usage
+
+### 1. Initialize a Project
+
+In your project root:
+
+```bash
+claude-code-conductor setup
+```
+
+This will:
+-   Analyze your project.
+-   Create the `conductor/` directory.
+-   Generate `product.md`, `tech-stack.md`, etc.
+
+### 2. Register Slash Commands
+
+To use Conductor inside Claude Code:
+
+```bash
+claude-code-conductor init
+```
+
+This registers `/conductor:setup`, `/conductor:implement`, etc., in your `.claude/commands/` directory.
+
+### 3. Start a Track
+
+```bash
+claude-code-conductor implement
+```
+
+Or inside Claude Code:
+
+```
+/conductor:implement
+```
+
+## Development
+
+```bash
+# Install dependencies
+npm install
+
+# Build
+npm run build
+
+# Run tests
+npm test
+```
+
+## License
+
+ISC

package/conductor/archive/init_cli_setup_20260107/metadata.json

@@ -0,0 +1,8 @@
+{
+    "track_id": "init_cli_setup_20260107",
+    "type": "feature",
+    "status": "new",
+    "created_at": "2026-01-07T00:00:00Z",
+    "updated_at": "2026-01-07T00:00:00Z",
+    "description": "Initialize the `claude-conductor` CLI project structure and implement the core `setup` command."
+}

package/conductor/archive/init_cli_setup_20260107/plan.md

@@ -0,0 +1,22 @@
+# Plan: Initialize CLI & Core Setup Command
+
+## Phase 1: Project Scaffolding [checkpoint: 75b2125]
+- [x] Task: Initialize npm project with `package.json` [1d8258b]
+- [x] Task: Configure TypeScript (`tsconfig.json`) with strict mode [251aaf6]
+- [x] Task: Configure ESLint and Prettier [14073fe]
+- [x] Task: Create project directory structure (`bin`, `src`, `templates`) [7492835]
+- [~] Task: Conductor - User Manual Verification 'Project Scaffolding' (Protocol in workflow.md)
+
+## Phase 2: Core CLI Infrastructure [checkpoint: 76c4681]
+- [x] Task: Install runtime dependencies (`commander`, `inquirer`, `chalk`, `ora`, `fs-extra`) [41c3df6]
+- [x] Task: Create CLI entry point `bin/claude-conductor.ts` and verify execution [7520ce5]
+- [x] Task: Implement basic `commander` program setup with version and help [46301a7]
+- [x] Task: Conductor - User Manual Verification 'Core CLI Infrastructure' (Protocol in workflow.md) [76c4681]
+
+## Phase 3: Project Discovery & Setup Wizard [checkpoint: 00d71fa]
+- [x] Task: Implement `conductor:setup` command stub and registration [5c8675a]
+- [x] Task: Implement `ProjectDiscovery` service (Greenfield/Brownfield detection logic) [8cae241]
+- [x] Task: Implement `SetupWizard` class with interactive prompts for Product Definition [741c96f]
+- [x] Task: Implement `FileGenerator` service to write `conductor/*.md` files [3d196f1]
+- [x] Task: Integrate Discovery, Wizard, and Generator into `conductor:setup` command [0ab5605]
+- [x] Task: Conductor - User Manual Verification 'Project Discovery & Setup Wizard' (Protocol in workflow.md) [00d71fa]

package/conductor/archive/init_cli_setup_20260107/spec.md

@@ -0,0 +1,78 @@
+# Specification: Initialize CLI & Core Setup Command
+
+## 1. Overview
+This track establishes the foundation of the `claude-conductor` npm package. It covers project scaffolding, TypeScript configuration, CLI entry point creation, and the implementation of the primary `conductor:setup` command. This command is responsible for initializing new projects or "adopting" existing ones (Brownfield) into the Conductor workflow.
+
+## 2. Requirements
+
+### 2.1 Project Scaffolding
+-   **Package Manager:** `npm`
+-   **Language:** TypeScript (Strict mode enabled)
+-   **Linter:** ESLint (with TypeScript support)
+-   **Formatter:** Prettier
+-   **Directory Structure:**
+    -   `bin/`: Executable entry points.
+    -   `src/`: Source code.
+    -   `conductor/`: Default templates (if applicable).
+    -   `dist/`: Compiled output.
+
+### 2.2 Core CLI Infrastructure
+-   **Dependencies:**
+    -   `commander`: For command-line argument parsing.
+    -   `inquirer`: For interactive command-line prompts.
+    -   `chalk`: For terminal styling.
+    -   `ora`: For loading spinners.
+    -   `fs-extra`: For file system operations.
+-   **Entry Point:** `bin/claude-conductor.ts` (mapped to `bin` in `package.json`).
+-   **Execution:** The CLI should be executable via `npx claude-conductor` or globally installed.
+
+### 2.3 Feature: Project Discovery
+-   **Logic:**
+    -   Check for `.git` directory to detect version control.
+    -   Check for `package.json`, `pom.xml`, etc., to detect "Brownfield" status.
+    -   If no indicators are found, classify as "Greenfield".
+-   **Output:** Display the detected project status to the user.
+
+### 2.4 Feature: Interactive Setup Wizard (`conductor:setup`)
+-   **Flow:**
+    1.  **Welcome Message:** Display "Welcome to Conductor..."
+    2.  **Project Discovery:** Run discovery logic (2.3).
+    3.  **Brownfield Handling:**
+        -   If Brownfield, warn about uncommitted changes.
+        -   Ask for permission to scan.
+    4.  **Product Definition:**
+        -   Ask "What do you want to build?" (Greenfield) or analyze `README.md` (Brownfield).
+        -   Generate `conductor/product.md`.
+    5.  **Tech Stack:**
+        -   Inquire about or detect the tech stack.
+        -   Generate `conductor/tech-stack.md`.
+    6.  **Product Guidelines:**
+        -   Inquire about tone/style.
+        -   Generate `conductor/product-guidelines.md`.
+    7.  **Finalization:**
+        -   Create `conductor/setup_state.json`.
+        -   Summary of actions.
+
+## 3. Implementation Details
+
+### 3.1 `package.json` Scripts
+-   `build`: `tsc`
+-   `start`: `node dist/index.js`
+-   `dev`: `ts-node src/index.ts`
+-   `lint`: `eslint src/**/*.ts`
+
+### 3.2 File Generation Templates
+-   The setup command should have embedded templates or write logic for:
+    -   `conductor/product.md`
+    -   `conductor/tech-stack.md`
+    -   `conductor/product-guidelines.md`
+    -   `conductor/setup_state.json`
+
+## 4. Acceptance Criteria
+-   [ ] `npm install` installs all required dependencies.
+-   [ ] `npm run build` compiles TypeScript without errors.
+-   [ ] Running the CLI executable works.
+-   [ ] `conductor:setup` correctly identifies an empty folder as Greenfield.
+-   [ ] `conductor:setup` correctly identifies a folder with `package.json` as Brownfield.
+-   [ ] The setup wizard successfully generates all required markdown files in the `conductor/` directory.
+-   [ ] `conductor/setup_state.json` is created with the correct completion state.

package/conductor/archive/npm_publish_20260107/metadata.json

@@ -0,0 +1,8 @@
+{
+  "track_id": "npm_publish_20260107",
+  "type": "feature",
+  "status": "new",
+  "created_at": "2026-01-07T00:00:00Z",
+  "updated_at": "2026-01-07T00:00:00Z",
+  "description": "The project is going to be published on npm. When installed in the user's workspace, Claude Code is going to get more commands from the package. Make sure that happens before git pushing it."
+}

package/conductor/archive/npm_publish_20260107/plan.md

@@ -0,0 +1,18 @@
+# Plan: NPM Publication & Slash Command Registration
+
+## Phase 1: NPM & CLI Configuration [checkpoint: 7daa017]
+- [x] Task: Audit and update `package.json` metadata (bin, main, files) and dependencies [5a699a6]
+- [x] Task: Implement `status` and `implement` command stubs in CLI to ensure targets exist [1e4a317]
+- [x] Task: Conductor - User Manual Verification 'NPM & CLI Configuration' (Protocol in workflow.md) [7daa017]
+- [ ] Task: Conductor - User Manual Verification 'NPM & CLI Configuration' (Protocol in workflow.md)
+
+## Phase 2: Init Command Implementation [checkpoint: a096ea3]
+- [x] Task: Create `init` command structure and register it in `bin/claude-conductor.ts` [e159a32]
+- [x] Task: Implement `CommandRegistrar` service to handle `.claude/commands` directory detection and creation [67671a5]
+- [x] Task: Implement logic to generate shell scripts/configs for `/conductor:*` commands [61005a6]
+- [x] Task: Conductor - User Manual Verification 'Init Command Implementation' (Protocol in workflow.md) [a096ea3]
+
+## Phase 3: Validation & Polish [checkpoint: 6ec0b1d]
+- [x] Task: Verify `npm publish --dry-run` succeeds [f7890a3]
+- [x] Task: End-to-end test: Run `init` and verify generated commands invoke the CLI correctly [236879e]
+- [x] Task: Conductor - User Manual Verification 'Validation & Polish' (Protocol in workflow.md) [6ec0b1d]

package/conductor/archive/npm_publish_20260107/spec.md

@@ -0,0 +1,34 @@
+# Specification: NPM Publication & Slash Command Registration
+
+## 1. Overview
+This track prepares the `claude-conductor` package for NPM publication and implements a mechanism to register its functionalities as custom slash commands within the user's Claude Code environment. The goal is to allow users to install the package and easily set up commands like `/conductor:setup`, `/conductor:implement`, and `/conductor:status` to boost their workflow productivity.
+
+## 2. Functional Requirements
+
+### 2.1 NPM Configuration
+-   **Package Metadata:** Ensure `package.json` is correctly configured for publication (name, version, description, main, bin).
+-   **Executable Bin:** Verify `bin/claude-conductor.ts` is correctly mapped in `package.json` to be executable via `npx` or global install.
+-   **Dependencies:** Audit dependencies to ensure `devDependencies` and `dependencies` are correctly separated.
+
+### 2.2 Command Registration (`init` command)
+-   **Trigger:** A new command `claude-conductor init` (or `npx claude-conductor init`) must be implemented.
+-   **Functionality:**
+    1.  **Detection:** Detect the presence of the `.claude/commands` directory in the user's workspace.
+    2.  **Creation:** If the directory does not exist, create it.
+    3.  **Registration:** Generate executable scripts or configuration files within `.claude/commands/` that map to the underlying `claude-conductor` CLI.
+        -   **Target Commands:**
+            -   `/conductor:setup` -> calls `claude-conductor setup`
+            -   `/conductor:implement` -> calls `claude-conductor implement` (placeholder if not yet implemented)
+            -   `/conductor:status` -> calls `claude-conductor status` (placeholder if not yet implemented)
+    4.  **Idempotency:** If the commands already exist, update them or skip gracefully (do not break existing configs).
+    5.  **Output:** Inform the user which commands were registered and how to use them.
+
+## 3. Non-Functional Requirements
+-   **Ease of Use:** The `init` process should be single-step and require minimal user intervention.
+-   **Safety:** Do not overwrite unrelated files in `.claude/commands`.
+
+## 4. Acceptance Criteria
+-   [ ] `package.json` passes `npm publish --dry-run` checks.
+-   [ ] Running `npx claude-conductor init` creates/updates the `.claude/commands` directory.
+-   [ ] After running `init`, files exist in `.claude/commands` corresponding to `setup`, `implement`, and `status`.
+-   [ ] These generated commands successfully invoke the `claude-conductor` CLI.

package/conductor/code_styleguides/javascript.md

@@ -0,0 +1,51 @@
+# Google JavaScript Style Guide Summary
+
+This document summarizes key rules and best practices from the Google JavaScript Style Guide.
+
+## 1. Source File Basics
+- **File Naming:** All lowercase, with underscores (`_`) or dashes (`-`). Extension must be `.js`.
+- **File Encoding:** UTF-8.
+- **Whitespace:** Use only ASCII horizontal spaces (0x20). Tabs are forbidden for indentation.
+
+## 2. Source File Structure
+- New files should be ES modules (`import`/`export`).
+- **Exports:** Use named exports (`export {MyClass};`). **Do not use default exports.**
+- **Imports:** Do not use line-wrapped imports. The `.js` extension in import paths is mandatory.
+
+## 3. Formatting
+- **Braces:** Required for all control structures (`if`, `for`, `while`, etc.), even single-line blocks. Use K&R style ("Egyptian brackets").
+- **Indentation:** +2 spaces for each new block.
+- **Semicolons:** Every statement must be terminated with a semicolon.
+- **Column Limit:** 80 characters.
+- **Line-wrapping:** Indent continuation lines at least +4 spaces.
+- **Whitespace:** Use single blank lines between methods. No trailing whitespace.
+
+## 4. Language Features
+- **Variable Declarations:** Use `const` by default, `let` if reassignment is needed. **`var` is forbidden.**
+- **Array Literals:** Use trailing commas. Do not use the `Array` constructor.
+- **Object Literals:** Use trailing commas and shorthand properties. Do not use the `Object` constructor.
+- **Classes:** Do not use JavaScript getter/setter properties (`get name()`). Provide ordinary methods instead.
+- **Functions:** Prefer arrow functions for nested functions to preserve `this` context.
+- **String Literals:** Use single quotes (`'`). Use template literals (`` ` ``) for multi-line strings or complex interpolation.
+- **Control Structures:** Prefer `for-of` loops. `for-in` loops should only be used on dict-style objects.
+- **`this`:** Only use `this` in class constructors, methods, or in arrow functions defined within them.
+- **Equality Checks:** Always use identity operators (`===` / `!==`).
+
+## 5. Disallowed Features
+- `with` keyword.
+- `eval()` or `Function(...string)`.
+- Automatic Semicolon Insertion.
+- Modifying builtin objects (`Array.prototype.foo = ...`).
+
+## 6. Naming
+- **Classes:** `UpperCamelCase`.
+- **Methods & Functions:** `lowerCamelCase`.
+- **Constants:** `CONSTANT_CASE` (all uppercase with underscores).
+- **Non-constant Fields & Variables:** `lowerCamelCase`.
+
+## 7. JSDoc
+- JSDoc is used on all classes, fields, and methods.
+- Use `@param`, `@return`, `@override`, `@deprecated`.
+- Type annotations are enclosed in braces (e.g., `/** @param {string} userName */`).
+
+*Source: [Google JavaScript Style Guide](https://google.github.io/styleguide/jsguide.html)*

package/conductor/code_styleguides/typescript.md

@@ -0,0 +1,43 @@
+# Google TypeScript Style Guide Summary
+
+This document summarizes key rules and best practices from the Google TypeScript Style Guide, which is enforced by the `gts` tool.
+
+## 1. Language Features
+- **Variable Declarations:** Always use `const` or `let`. **`var` is forbidden.** Use `const` by default.
+- **Modules:** Use ES6 modules (`import`/`export`). **Do not use `namespace`.**
+- **Exports:** Use named exports (`export {MyClass};`). **Do not use default exports.**
+- **Classes:**
+  - **Do not use `#private` fields.** Use TypeScript's `private` visibility modifier.
+  - Mark properties never reassigned outside the constructor with `readonly`.
+  - **Never use the `public` modifier** (it's the default). Restrict visibility with `private` or `protected` where possible.
+- **Functions:** Prefer function declarations for named functions. Use arrow functions for anonymous functions/callbacks.
+- **String Literals:** Use single quotes (`'`). Use template literals (`` ` ``) for interpolation and multi-line strings.
+- **Equality Checks:** Always use triple equals (`===`) and not equals (`!==`).
+- **Type Assertions:** **Avoid type assertions (`x as SomeType`) and non-nullability assertions (`y!`)**. If you must use them, provide a clear justification.
+
+## 2. Disallowed Features
+- **`any` Type:** **Avoid `any`**. Prefer `unknown` or a more specific type.
+- **Wrapper Objects:** Do not instantiate `String`, `Boolean`, or `Number` wrapper classes.
+- **Automatic Semicolon Insertion (ASI):** Do not rely on it. **Explicitly end all statements with a semicolon.**
+- **`const enum`:** Do not use `const enum`. Use plain `enum` instead.
+- **`eval()` and `Function(...string)`:** Forbidden.
+
+## 3. Naming
+- **`UpperCamelCase`:** For classes, interfaces, types, enums, and decorators.
+- **`lowerCamelCase`:** For variables, parameters, functions, methods, and properties.
+- **`CONSTANT_CASE`:** For global constant values, including enum values.
+- **`_` Prefix/Suffix:** **Do not use `_` as a prefix or suffix** for identifiers, including for private properties.
+
+## 4. Type System
+- **Type Inference:** Rely on type inference for simple, obvious types. Be explicit for complex types.
+- **`undefined` and `null`:** Both are supported. Be consistent within your project.
+- **Optional vs. `|undefined`:** Prefer optional parameters and fields (`?`) over adding `|undefined` to the type.
+- **`Array<T>` Type:** Use `T[]` for simple types. Use `Array<T>` for more complex union types (e.g., `Array<string | number>`).
+- **`{}` Type:** **Do not use `{}`**. Prefer `unknown`, `Record<string, unknown>`, or `object`.
+
+## 5. Comments and Documentation
+- **JSDoc:** Use `/** JSDoc */` for documentation, `//` for implementation comments.
+- **Redundancy:** **Do not declare types in `@param` or `@return` blocks** (e.g., `/** @param {string} user */`). This is redundant in TypeScript.
+- **Add Information:** Comments must add information, not just restate the code.
+
+*Source: [Google TypeScript Style Guide](https://google.github.io/styleguide/tsguide.html)*

package/conductor/product-guidelines.md

@@ -0,0 +1,16 @@
+# Product Guidelines: Claude Code Conductor
+
+## Prose & Tone
+-   **Tone:** Professional, Minimalist, Direct.
+-   **Voice:** The CLI should speak as a tool, not a person. Avoid "I will..." or "Let's...". Use imperative verbs (e.g., "Analyzing project...", "Generating plan...").
+-   **Verbosity:** Concise. Provide only essential information. Success messages should be brief. Errors should be actionable.
+
+## Visual Identity (CLI)
+-   **Formatting:** Use standard ANSI colors for status indicators (Green=Success, Yellow=Warning, Red=Error).
+-   **Structure:** Use whitespace effectively to separate distinct sections of output.
+-   **Decorations:** Minimal. Avoid excessive emojis or ASCII art. Use standard loading spinners for long-running processes.
+
+## Interaction Patterns
+-   **Input:** Default to "Yes/No" or numeric selection for multiple choices.
+-   **Defaults:** Always provide sensible defaults for prompts (displayed in brackets, e.g., `[Y/n]`).
+-   **Confirmation:** Require explicit confirmation for destructive actions.

package/conductor/product.md

@@ -0,0 +1,20 @@
+# Product Guide: Claude Code Conductor
+
+## Initial Concept
+Create an npm package for Claude code to be a wrapper around Claude code. Make it be exactly like Gemini cli conductor. Research multiple websites and sources before building.
+
+## Product Vision
+To provide a structured, context-driven development workflow for Claude Code users, mirroring the functionality of the Gemini CLI Conductor. This tool will act as a project manager, ensuring AI agents adhere to consistent documentation and plans.
+
+## Core Features
+-   **Project Initialization:** Interactive wizard to classify projects (Greenfield/Brownfield) and set up the `conductor/` directory structure.
+-   **Command Integration:** Automated registration of `conductor` commands (`setup`, `implement`, `status`) as native slash commands in the Claude Code environment.
+-   **Context Management:** Automated generation and maintenance of `product.md`, `tech-stack.md`, and `product-guidelines.md`.
+-   **Track System:** A "Tracks" based workflow (`tracks.md`) to manage feature development.
+-   **Planning Engine:** Automated generation of detailed `plan.md` and `spec.md` files for each track.
+-   **CLI Wrapper:** A unified CLI command (e.g., `claude-code-conductor`) that wraps the underlying Claude Code execution.
+
+## User Experience
+-   **Interactive Mode:** CLI prompts for setup and decision-making.
+-   **Automated Execution:** "Implement" mode to execute plans step-by-step.
+-   **Transparency:** All context and state are stored in readable Markdown/JSON files within the user's project.

package/conductor/setup_state.json

@@ -0,0 +1 @@
+{"last_successful_step": "3.3_initial_track_generated"}

package/conductor/tech-stack.md

@@ -0,0 +1,19 @@
+# Tech Stack: Claude Code Conductor
+
+## Core Runtime
+-   **Language:** TypeScript
+-   **Runtime:** Node.js
+-   **Package Manager:** npm
+
+## CLI Framework
+-   **Library:** Commander.js
+-   **Interactivity:** Inquirer.js
+-   **Styling:** Chalk (for terminal coloring), Ora (for spinners)
+
+## Integration
+-   **AI Engine:** Claude Code (via `claude` CLI execution)
+-   **Context Storage:** Markdown (`.md`) and JSON (`.json`) files
+
+## Testing
+-   **Framework:** Jest
+-   **Runner:** ts-jest

package/conductor/tracks/rename_cli_20260107/metadata.json

@@ -0,0 +1,8 @@
+{
+  "track_id": "rename_cli_20260107",
+  "type": "feature",
+  "status": "new",
+  "created_at": "2026-01-07T00:00:00Z",
+  "updated_at": "2026-01-07T00:00:00Z",
+  "description": "Rename claude-conductor to claude-code-conductor"
+}

package/conductor/tracks/rename_cli_20260107/plan.md

@@ -0,0 +1,25 @@
+# Implementation Plan - Rename to Claude Code Conductor
+
+## Phase 1: Package Identity Update [checkpoint: 28105d0]
+- [x] Task: Update Package Configuration 0249499
+    - [ ] Sub-task: Create a test that reads `package.json` and asserts name is `claude-code-conductor` (Red)
+    - [ ] Sub-task: Update `package.json` name, description, and bin entry (Green)
+    - [ ] Sub-task: Update `package-lock.json` (Green)
+- [ ] Task: Conductor - User Manual Verification 'Phase 1: Package Identity Update' (Protocol in workflow.md)
+
+## Phase 2: CLI & Source Code Refactor [checkpoint: de93efc]
+- [x] Task: Rename Binary Entry Point 24daa4a
+    - [ ] Sub-task: Rename `bin/claude-conductor.ts` to `bin/claude-code-conductor.ts`
+    - [ ] Sub-task: Verify `tsconfig.json` includes the new bin path (it uses glob `bin/**/*` so it should be fine, but verification is needed)
+- [x] Task: Update CLI Output & Strings ab559a1
+    - [ ] Sub-task: Update existing tests to expect "Claude Code Conductor" in help/version output (Red)
+    - [ ] Sub-task: Search and replace user-facing strings in `src/` (Green)
+    - [ ] Sub-task: Verify all tests pass (Refactor)
+- [ ] Task: Conductor - User Manual Verification 'Phase 2: CLI & Source Code Refactor' (Protocol in workflow.md)
+
+## Phase 3: Documentation Updates [checkpoint: cb23914]
+- [x] Task: Update Project Documentation d62274d
+    - [ ] Sub-task: Update `README.md` with new command usage
+    - [ ] Sub-task: Update `conductor/` files (`product.md`, `tech-stack.md`)
+    - [ ] Sub-task: Update `CLAUDE.md` and `QUICKSTART.md` if applicable
+- [ ] Task: Conductor - User Manual Verification 'Phase 3: Documentation Updates' (Protocol in workflow.md)