@dezkareid/osddt 1.3.0 → 1.3.2

package/AGENTS.md

@@ -138,7 +138,7 @@ All commands available via `npx @dezkareid/osddt <command>`:
 | `@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>`                               | Move `working-on/<feature>` to `done/<feature>`               |
+| `@dezkareid/osddt done <feature-name> --dir <project-path>`          | Move `working-on/<feature>` to `done/<feature>`               |
 
 #### `osddt setup` options
 
@@ -163,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
 
@@ -214,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

@@ -8,7 +8,7 @@ Other spec driven development tool but for monorepo
 | `@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>`                               | Move `working-on/<feature>` to `done/<feature>`               |
+| `@dezkareid/osddt done <feature-name> --dir <project-path>`          | Move `working-on/<feature>` to `done/<feature>`               |
 
 ### `osddt setup` options
 
@@ -51,7 +51,7 @@ 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:
 

package/dist/index.js

@@ -192,19 +192,21 @@ Run the following command to write the feature specification:
    - If it does not exist, proceed using only the requirements provided in ${args}.
 2. Analyze the requirements provided in ${args}
 3. Identify the core problem being solved
-4. Define the scope, constraints, and acceptance criteria
+4. Define the scope, user-facing constraints, and acceptance criteria
 5. Write the specification to \`osddt.spec.md\` in the working directory
 
 ## Specification Format
 
+The spec should describe **what** the feature does and **why**, from a product and user perspective. Do **not** include implementation details, technology choices, or technical architecture — those belong in the plan.
+
 The spec should include:
-- **Overview**: What and why
-- **Requirements**: Functional and non-functional
-- **Scope**: What is in and out of scope
-- **Acceptance Criteria**: Clear, testable criteria
-- **Open Questions**: Any ambiguities to resolve
+- **Overview**: What the feature is and why it is needed
+- **Requirements**: Functional requirements only — what the system must do, expressed as user-observable behaviours
+- **Scope**: What is in and out of scope, described in product terms
+- **Acceptance Criteria**: Clear, testable criteria written from a user or business perspective
+- **Open Questions**: Ambiguities about desired behaviour or product decisions to resolve
 
-> If \`osddt.research.md\` was found, add a **Research Summary** section that briefly references the key insights and constraints it identified.
+> If \`osddt.research.md\` was found, add a **Research Summary** section that briefly references the key insights and user-facing constraints it identified.
 
 ## Arguments
 
@@ -332,17 +334,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
 
@@ -531,16 +538,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.3.0",
+  "version": "1.3.2",
   "description": "Package for Spec-Driven Development workflow",
   "keywords": [
     "spec-driven",