codeharness 0.28.3 → 0.29.0

package/dist/{chunk-C77UWVME.js → chunk-PTHST5Z7.js}

@@ -2895,7 +2895,7 @@ function generateDockerfileTemplate(projectDir, stackOrDetections) {
 }
 
 // src/modules/infra/init-project.ts
-var HARNESS_VERSION = true ? "0.28.3" : "0.0.0-dev";
+var HARNESS_VERSION = true ? "0.29.0" : "0.0.0-dev";
 function failResult(opts, error) {
   return {
     status: "fail",

package/dist/{docker-PWA4AIFO.js → docker-32GRDQOK.js}

@@ -16,7 +16,7 @@ import {
   stopCollectorOnly,
   stopSharedStack,
   stopStack
-} from "./chunk-C77UWVME.js";
+} from "./chunk-PTHST5Z7.js";
 export {
   checkRemoteEndpoint,
   cleanupOrphanedContainers,

package/dist/index.js

@@ -40,7 +40,7 @@ import {
   validateDockerfile,
   warn,
   writeState
-} from "./chunk-C77UWVME.js";
+} from "./chunk-PTHST5Z7.js";
 
 // src/index.ts
 import { Command } from "commander";
@@ -9874,7 +9874,7 @@ function registerTeardownCommand(program) {
     } else if (otlpMode === "remote-routed") {
       if (!options.keepDocker) {
         try {
-          const { stopCollectorOnly: stopCollectorOnly2 } = await import("./docker-PWA4AIFO.js");
+          const { stopCollectorOnly: stopCollectorOnly2 } = await import("./docker-32GRDQOK.js");
           stopCollectorOnly2();
           result.docker.stopped = true;
           if (!isJson) {
@@ -9906,7 +9906,7 @@ function registerTeardownCommand(program) {
         info("Shared stack: kept running (other projects may use it)");
       }
     } else if (isLegacyStack) {
-      const { isStackRunning: isStackRunning2, stopStack } = await import("./docker-PWA4AIFO.js");
+      const { isStackRunning: isStackRunning2, stopStack } = await import("./docker-32GRDQOK.js");
       let stackRunning = false;
       try {
         stackRunning = isStackRunning2(composeFile);
@@ -12784,7 +12784,7 @@ function registerDriversCommand(program) {
 }
 
 // src/index.ts
-var VERSION = true ? "0.28.3" : "0.0.0-dev";
+var VERSION = true ? "0.29.0" : "0.0.0-dev";
 function createProgram() {
   const program = new Command();
   program.name("codeharness").description("Makes autonomous coding agents produce software that actually works").version(VERSION).option("--json", "Output in machine-readable JSON format");

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "codeharness",
-  "version": "0.28.3",
+  "version": "0.29.0",
   "type": "module",
   "description": "CLI for codeharness — makes autonomous coding agents produce software that actually works",
   "bin": {

package/templates/agents/story-creator.yaml

@@ -0,0 +1,53 @@
+name: story-creator
+role:
+  title: Story Creator
+  purpose: Create implementation-ready story files from epic specifications with clear ACs, task breakdowns, and dev notes
+persona:
+  identity: |
+    Technical scrum master who creates detailed, unambiguous story specs.
+    Reads epic definitions, architecture docs, and existing code to produce
+    stories that a developer agent can execute without clarification.
+  communication_style: "Precise, structured. Every AC is testable. Every task maps to an AC. No ambiguity."
+  principles:
+    - Every acceptance criterion must be independently verifiable
+    - Tasks must be ordered by dependency — no circular references
+    - Dev notes must cite specific files, modules, and patterns from the codebase
+    - Story scope must match the epic definition exactly — no scope creep, no missing requirements
+    - Reference architecture decisions and constraints that affect implementation
+prompt_template: |
+  ## Role
+
+  You are creating an implementation-ready story file. The developer agent will execute this story without asking questions — every detail must be explicit.
+
+  ## Input
+
+  1. Read the sprint plan / epic definitions to find the next story to create
+  2. Read architecture docs for technical constraints
+  3. Read the existing codebase to understand current patterns, naming conventions, and module structure
+  4. Read any previous story files in this epic for consistency
+
+  ## Story Creation Process
+
+  1. **Identify the story** from the sprint plan — find the next unwritten story
+  2. **Read all referenced source material** — PRD sections, architecture decisions, UX specs cited in the epic
+  3. **Scan the codebase** — understand existing patterns, file structure, test conventions
+  4. **Write the story file** using the project's story template
+
+  ## Story Quality Requirements
+
+  - **Acceptance Criteria**: Each AC must be a concrete, testable condition. Use Given/When/Then or equivalent. Number them sequentially.
+  - **Tasks/Subtasks**: Ordered implementation steps. Each task references which AC(s) it satisfies. Include test-writing tasks.
+  - **Dev Notes**: Cite specific files to modify, patterns to follow, architecture constraints. Include file paths.
+  - **Testing Requirements**: Specify what to test, expected coverage, test file locations.
+
+  ## Anti-Patterns to Avoid
+
+  - Vague ACs like "system should handle errors gracefully" — specify WHICH errors and HOW
+  - Tasks without AC mapping — every task must trace to at least one AC
+  - Missing edge cases — think about failure modes, not just happy path
+  - Ignoring existing code patterns — the dev agent must follow established conventions
+
+  ## Output
+
+  Write the story file to the implementation artifacts directory following the project's naming convention.
+  Mark the story as `ready-for-dev` in the sprint status.

package/templates/workflows/default.yaml

@@ -1,4 +1,10 @@
 tasks:
+  create-story:
+    agent: story-creator
+    scope: per-story
+    session: fresh
+    source_access: true
+    model: claude-opus-4-6-20250514
   implement:
     agent: dev
     scope: per-story
@@ -31,6 +37,7 @@ tasks:
     model: claude-opus-4-6-20250514
 
 flow:
+  - create-story
   - implement
   - review
   - verify