@dezkareid/osddt 1.2.0 → 1.3.1

package/AGENTS.md

@@ -103,7 +103,7 @@ osddt/
 ├── src/
 │   ├── index.ts                   # CLI entry point — wires Commander program and registers all commands
 │   ├── commands/
-│   │   ├── setup.ts               # `osddt setup` — prompts for agents & repo type, writes command files and .osddtrc
+│   │   ├── setup.ts               # `osddt setup` — prompts for agents & repo type (or reads --agents/--repo-type flags), writes command files and .osddtrc
 │   │   ├── meta-info.ts           # `osddt meta-info` — outputs { branch, date } as JSON (consumed by generated templates)
 │   │   └── done.ts                # `osddt done <feature>` — moves working-on/<feature> → done/YYYY-MM-DD-<feature>
 │   ├── templates/
@@ -125,7 +125,7 @@ osddt/
 #### Key relationships
 
 - **`shared.ts` is the single source of truth** for all command template content. Both `claude.ts` and `gemini.ts` import `COMMAND_DEFINITIONS` from it and only differ in file format (Markdown vs TOML) and argument placeholder (`$ARGUMENTS` vs `{{args}}`).
-- **`setup.ts`** orchestrates the interactive setup: calls `askAgents()` → `askRepoType()` → writes selected agent files → writes `.osddtrc`.
+- **`setup.ts`** orchestrates setup: reads `--agents`/`--repo-type` flags when provided (non-interactive), otherwise calls `askAgents()` → `askRepoType()` → writes selected agent files → writes `.osddtrc`.
 - **`meta-info.ts`** is referenced inside the generated templates so agents can fetch live branch/date at invocation time (not baked in at build time).
 - **Test files** (`.spec.ts`) live next to the source file they cover. Template tests are pure (no mocks); command tests mock `fs-extra` and `child_process`.
 
@@ -133,11 +133,22 @@ osddt/
 
 All commands available via `npx @dezkareid/osddt <command>`:
 
-| Command                        | Description                                                   |
-| ------------------------------ | ------------------------------------------------------------- |
-| `@dezkareid/osddt setup`                  | Generate agent command files for Claude and Gemini            |
-| `@dezkareid/osddt meta-info`              | Output current branch and date as JSON                        |
-| `@dezkareid/osddt done <feature-name>`    | Move `working-on/<feature>` to `done/<feature>`               |
+| Command                                                              | Description                                                   |
+| -------------------------------------------------------------------- | ------------------------------------------------------------- |
+| `@dezkareid/osddt setup`                                             | Generate agent command files for Claude and Gemini            |
+| `@dezkareid/osddt setup --agents <list> --repo-type <type>`          | Non-interactive setup (for CI/scripted environments)          |
+| `@dezkareid/osddt meta-info`                                         | Output current branch and date as JSON                        |
+| `@dezkareid/osddt done <feature-name> --dir <project-path>`          | Move `working-on/<feature>` to `done/<feature>`               |
+
+#### `osddt setup` options
+
+| Flag | Values | Description |
+| ---- | ------ | ----------- |
+| `--agents <list>` | `claude`, `gemini` (comma-separated) | Skip the agents prompt and use the provided value(s) |
+| `--repo-type <type>` | `single`, `monorepo` | Skip the repo type prompt and use the provided value |
+| `-d, --dir <directory>` | any path | Target directory (defaults to current working directory) |
+
+Both flags are optional. Providing neither runs the fully interactive mode. Providing both skips all prompts.
 
 ### Command Templates
 
@@ -152,7 +163,7 @@ Templates are generated by `npx @dezkareid/osddt setup` and placed in each agent
 | `osddt.plan`       | Create a technical implementation plan from a specification        |
 | `osddt.tasks`      | Generate actionable tasks from an implementation plan              |
 | `osddt.implement`  | Execute tasks from the task list one by one                        |
-| `osddt.done`       | Mark a feature as done and move it from working-on to done         |
+| `osddt.done`       | Resolve project path, verify tasks, and move the feature to done   |
 
 #### Template Workflow
 
@@ -203,6 +214,17 @@ osddt.start    ──┘
   2. Checks for an existing `working-on/<feature-name>/` folder — offers **Resume** or **Abort** if found, otherwise creates it.
   3. Researches the topic (codebase exploration, external references) and writes `osddt.research.md`.
 
+#### osddt.done behaviour
+
+- **Input**: A feature name or branch name identifying the feature to close.
+- **Actions performed by the agent**:
+  1. Reads `.osddtrc` to resolve the project path (single vs monorepo). For monorepos, asks the user which package.
+  2. Derives the feature name from the input (same rules as other commands — last segment of a branch name or kebab-cased slug, subject to the 30-character limit). Must match the folder under `working-on/`.
+  3. Confirms all tasks in `osddt.tasks.md` are checked off (`- [x]`).
+  4. Runs `npx @dezkareid/osddt done <feature-name> --dir <project-path>` to move the folder.
+
+Note: the `osddt done` CLI command does **not** read `.osddtrc` — project path resolution is the agent's responsibility, handled in step 1 above.
+
 ### Template Data Convention
 
 When a template needs dynamic information (e.g. current branch, date, repo config), **do not pass it as a build-time argument**. Instead:

package/README.md

@@ -3,11 +3,30 @@ Other spec driven development tool but for monorepo
 
 ## CLI Commands
 
-| Command                        | Description                                                   |
-| ------------------------------ | ------------------------------------------------------------- |
-| `@dezkareid/osddt setup`                  | Generate agent command files for Claude and Gemini            |
-| `@dezkareid/osddt meta-info`              | Output current branch and date as JSON                        |
-| `@dezkareid/osddt done <feature-name>`    | Move `working-on/<feature>` to `done/<feature>`               |
+| Command                                                              | Description                                                   |
+| -------------------------------------------------------------------- | ------------------------------------------------------------- |
+| `@dezkareid/osddt setup`                                             | Generate agent command files for Claude and Gemini            |
+| `@dezkareid/osddt setup --agents <list> --repo-type <type>`          | Non-interactive setup (for CI/scripted environments)          |
+| `@dezkareid/osddt meta-info`                                         | Output current branch and date as JSON                        |
+| `@dezkareid/osddt done <feature-name> --dir <project-path>`          | Move `working-on/<feature>` to `done/<feature>`               |
+
+### `osddt setup` options
+
+| Flag | Values | Description |
+| ---- | ------ | ----------- |
+| `--agents <list>` | `claude`, `gemini` (comma-separated) | Skip the agents prompt and use the provided value(s) |
+| `--repo-type <type>` | `single`, `monorepo` | Skip the repo type prompt and use the provided value |
+| `-d, --dir <directory>` | any path | Target directory (defaults to current working directory) |
+
+Both flags are optional. Providing neither runs the fully interactive mode. Providing both skips all prompts.
+
+```bash
+# Interactive (default)
+npx @dezkareid/osddt setup
+
+# Non-interactive (CI-friendly)
+npx @dezkareid/osddt setup --agents claude,gemini --repo-type single
+```
 
 ## Command Templates
 
@@ -32,9 +51,31 @@ osddt.start    ──┘
 | `osddt.plan`       | Create a technical implementation plan from a specification        |
 | `osddt.tasks`      | Generate actionable tasks from an implementation plan              |
 | `osddt.implement`  | Execute tasks from the task list one by one                        |
-| `osddt.done`       | Mark a feature as done and move it from working-on to done         |
+| `osddt.done`       | Resolve project path, verify tasks, and move the feature to done   |
 
 Generated files are placed in:
 
 - `.claude/commands/osddt.<name>.md` (Claude Code)
 - `.gemini/commands/osddt.<name>.toml` (Gemini CLI)
+
+## Development
+
+### Running Tests
+
+```bash
+# Run the full test suite once
+pnpm test
+
+# Run in watch mode during development
+pnpm run test:watch
+```
+
+### Local Setup
+
+After making changes to the source, rebuild and regenerate the agent command files in the repository:
+
+```bash
+pnpm run setup-local
+```
+
+This runs `pnpm run build` followed by `npx osddt setup`, prompting you to select which agents to configure and the repo type.

package/dist/commands/setup.spec.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/index.js

@@ -224,13 +224,13 @@ Run the following command to create the implementation plan:
         description: 'Create a technical implementation plan from a specification',
         body: (args) => `## Instructions
 
-1. Read \`osddt.spec.md\` from the working directory
-2. Check whether \`osddt.plan.md\` already exists in the working directory:
+1. Check whether \`osddt.plan.md\` already exists in the working directory:
    - If it **does not exist**, proceed to generate it.
    - If it **already exists**, ask the user whether to:
      - **Regenerate** — discard the existing file and create a fresh plan from scratch
      - **Update** — read the existing file and apply targeted changes based on ${args}
      - **Do nothing** — stop here and leave the file as-is
+2. Read \`osddt.spec.md\` from the working directory
 3. Break down the implementation into logical phases and steps
 4. Identify technical decisions, dependencies, and risks
 5. Write the plan to \`osddt.plan.md\` in the working directory
@@ -262,13 +262,13 @@ Run the following command to generate the task list:
         description: 'Generate actionable tasks from an implementation plan',
         body: (args) => `## Instructions
 
-1. Read \`osddt.plan.md\` from the working directory
-2. Check whether \`osddt.tasks.md\` already exists in the working directory:
+1. Check whether \`osddt.tasks.md\` already exists in the working directory:
    - If it **does not exist**, proceed to generate it.
    - If it **already exists**, ask the user whether to:
      - **Regenerate** — discard the existing file and create a fresh task list from scratch
      - **Update** — read the existing file and apply targeted changes based on ${args}
      - **Do nothing** — stop here and leave the file as-is
+2. Read \`osddt.plan.md\` from the working directory
 3. Break each phase into discrete, executable tasks
 4. Estimate complexity (S/M/L) for each task
 5. Write the task list to \`osddt.tasks.md\` in the working directory
@@ -301,10 +301,6 @@ Run the following command to start implementing tasks:
 
 1. Check whether \`osddt.tasks.md\` exists in the working directory:
    - If it **does not exist**, stop and ask the user to run \`/osddt.tasks ${args}\` first.
-   - If it **already exists**, ask the user whether to:
-     - **Continue** — find the next unchecked task and implement it (default)
-     - **Update tasks** — edit \`osddt.tasks.md\` before implementing (e.g. to add, remove, or reorder tasks)
-     - **Do nothing** — stop here without making any changes
 2. Read \`osddt.tasks.md\` from the working directory
 3. Find the next unchecked task (\`- [ ]\`)
 4. Implement that task following the spec (\`osddt.spec.md\`) and plan (\`osddt.plan.md\`) in the working directory
@@ -336,17 +332,22 @@ Once all tasks are checked off, run the following command to mark the feature as
         description: 'Mark a feature as done and move it from working-on to done',
         body: (args) => `## Instructions
 
-1. Confirm all tasks in \`osddt.tasks.md\` are checked off (\`- [x]\`)
-2. Run the following command to move the feature folder from \`working-on\` to \`done\`:
+1. Resolve the project path:
+   - Read \`.osddtrc\` from the repository root.
+   - If \`repoType\` is \`"single"\`: the project path is the repository root.
+   - If \`repoType\` is \`"monorepo"\`: ask the user which package to work on (e.g. \`packages/my-package\`), then use \`<repo-root>/<package>\` as the project path.
+2. Derive the feature name from ${args} using the same rules as the other commands (last segment of a branch name, or a kebab-cased slug — subject to the 30-character limit). This must match the folder name under \`working-on/\`.
+3. Confirm all tasks in \`osddt.tasks.md\` are checked off (\`- [x]\`)
+4. Run the following command to move the feature folder from \`working-on\` to \`done\`:
 
 \`\`\`
-npx @dezkareid/osddt done ${args}
+npx @dezkareid/osddt done <feature-name> --dir <project-path>
 \`\`\`
 
    The command will automatically prefix the destination folder name with today's date in \`YYYY-MM-DD\` format.
    For example, \`working-on/feature-a\` will be moved to \`done/YYYY-MM-DD-feature-a\`.
 
-3. Report the result of the command, including the full destination path
+5. Report the result of the command, including the full destination path
 
 ## Arguments
 
@@ -428,6 +429,28 @@ async function askAgents() {
     });
 }
 
+const VALID_AGENTS = ['claude', 'gemini'];
+const VALID_REPO_TYPES = ['single', 'monorepo'];
+function parseAgents(raw) {
+    const values = raw.split(',').map((s) => s.trim());
+    if (values.length === 0) {
+        console.error('Error: --agents requires at least one value.');
+        process.exit(1);
+    }
+    const invalid = values.filter((v) => !VALID_AGENTS.includes(v));
+    if (invalid.length > 0) {
+        console.error(`Error: Invalid agent(s): ${invalid.join(', ')}. Valid values: ${VALID_AGENTS.join(', ')}.`);
+        process.exit(1);
+    }
+    return values;
+}
+function parseRepoType(raw) {
+    if (!VALID_REPO_TYPES.includes(raw)) {
+        console.error(`Error: Invalid repo type: "${raw}". Valid values: ${VALID_REPO_TYPES.join(', ')}.`);
+        process.exit(1);
+    }
+    return raw;
+}
 async function writeCommandFile(file) {
     await fs.ensureDir(path.dirname(file.filePath));
     await fs.writeFile(file.filePath, file.content, 'utf-8');
@@ -438,11 +461,13 @@ async function writeConfig(cwd, config) {
     await fs.writeJson(configPath, config, { spaces: 2 });
     console.log(`\nSaved config: ${configPath}`);
 }
-async function runSetup(cwd) {
-    const agents = await askAgents();
-    console.log('');
-    const repoType = await askRepoType();
-    console.log('');
+async function runSetup(cwd, rawAgents, rawRepoType) {
+    const agents = rawAgents !== undefined ? parseAgents(rawAgents) : await askAgents();
+    if (rawAgents === undefined)
+        console.log('');
+    const repoType = rawRepoType !== undefined ? parseRepoType(rawRepoType) : await askRepoType();
+    if (rawRepoType === undefined)
+        console.log('');
     console.log('Setting up OSDDT command files...\n');
     if (agents.includes('claude')) {
         const claudeFiles = getClaudeTemplates(cwd);
@@ -469,9 +494,11 @@ function setupCommand() {
     cmd
         .description('Create OSDDT command files for Claude and Gemini CLI agents')
         .option('-d, --dir <directory>', 'target directory', process.cwd())
+        .option('--agents <list>', 'comma-separated agents to set up (claude, gemini)')
+        .option('--repo-type <type>', 'repository type (single, monorepo)')
         .action(async (options) => {
         const targetDir = path.resolve(options.dir);
-        await runSetup(targetDir);
+        await runSetup(targetDir, options.agents, options.repoType);
     });
     return cmd;
 }
@@ -509,16 +536,9 @@ function todayPrefix() {
     return `${yyyy}-${mm}-${dd}`;
 }
 async function runDone(featureName, cwd) {
-    const configPath = path.join(cwd, '.osddtrc');
-    if (!(await fs.pathExists(configPath))) {
-        console.error('Error: .osddtrc not found. Run `osddt setup` first.');
-        process.exit(1);
-    }
-    await fs.readJson(configPath);
-    const projectPath = cwd;
-    const src = path.join(projectPath, 'working-on', featureName);
+    const src = path.join(cwd, 'working-on', featureName);
     const destName = `${todayPrefix()}-${featureName}`;
-    const dest = path.join(projectPath, 'done', destName);
+    const dest = path.join(cwd, 'done', destName);
     if (!(await fs.pathExists(src))) {
         console.error(`Error: working-on/${featureName} does not exist.`);
         process.exit(1);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@dezkareid/osddt",
-  "version": "1.2.0",
+  "version": "1.3.1",
   "description": "Package for Spec-Driven Development workflow",
   "keywords": [
     "spec-driven",
@@ -56,6 +56,6 @@
     "test:watch": "vitest",
     "lint": "eslint src",
     "format": "prettier --write src",
-    "setup-local": "pnpm run build && npx osddt setup"
+    "setup-local": "pnpm run build && npx osddt setup --agents claude --repo-type single"
   }
 }