openplanr 0.9.0 → 1.0.0

package/dist/templates/rules/claude/CLAUDE.md.hbs

@@ -1,52 +1,95 @@
-# {{projectName}} — Agile Planning Guide
+# {{projectName}} — Agile Planning & Implementation Guide
 
 > Generated by OpenPlanr on {{date}}
 
-## Project Structure
-
 This project uses OpenPlanr for agile planning. All artifacts are in `{{agilePath}}/`.
 
-### Artifact Locations
-- **Epics:** `{{agilePath}}/epics/`
-- **Features:** `{{agilePath}}/features/`
-- **User Stories:** `{{agilePath}}/stories/`
-- **Tasks:** `{{agilePath}}/tasks/`
-- **ADRs:** `{{agilePath}}/adrs/`
-- **Checklist:** `{{agilePath}}/checklists/AGILE-DEVELOPMENT-GUIDE.md`
+## Context-Gathering Protocol
+
+Before implementing ANY task or subtask, you MUST gather full planning context by reading the artifact hierarchy. Follow this exact sequence:
+
+### Step 1: Read the Task List
+- Open the task file from `{{agilePath}}/tasks/` (e.g., `TASK-001-*.md`) or quick task from `{{agilePath}}/quick/`
+- Parse the frontmatter to find `storyId` or `featureId`
+- Identify the target subtask (first unchecked `- [ ]` item)
+- Read ALL subtasks to understand the full scope and dependencies
+
+### Step 2: Read the Parent Chain (MANDATORY)
+Follow the artifact hierarchy upward — each level adds critical context:
+
+1. **User Story** → `{{agilePath}}/stories/US-XXX-*.md`
+   - Read the full story (role, goal, benefit, acceptance criteria)
+   - Find and read the matching Gherkin file: `{{agilePath}}/stories/US-XXX-gherkin.feature`
+   - Extract the parent `featureId` from frontmatter
+
+2. **Feature** → `{{agilePath}}/features/FEAT-XXX-*.md`
+   - Read the full feature (overview, functional requirements, technical considerations)
+   - Extract the parent `epicId` from frontmatter
+
+3. **Epic** → `{{agilePath}}/epics/EPIC-XXX-*.md`
+   - Read the epic summary (business value, problem statement, success criteria)
+   - This provides the WHY behind the work
+
+### Step 3: Read Architecture Context
+- Read ALL ADRs in `{{agilePath}}/adrs/` — these are binding technical decisions
+- Check `{{agilePath}}/checklists/AGILE-DEVELOPMENT-GUIDE.md` for current progress
+
+### Step 4: Scan the Codebase
+Before writing code, understand what exists:
 
-## Agile Workflow
+1. **Identify the tech stack** — Read `package.json`, `tsconfig.json`, or equivalent
+2. **Scan the source tree** — List directories under `src/` (or project root)
+3. **Read architecture files** — Look for these high-priority files:
+   - Type definitions: `src/models/types.ts`, `src/types/index.ts`, or `src/types.ts`
+   - Core services: `src/services/` — understand CRUD patterns
+   - Entry point: `src/index.ts`, `src/main.ts`, or `src/app.ts` — understand registration patterns
+   - Config: `src/config.ts` or `src/services/config-service.ts`
+4. **Find related files** — Search for files matching keywords from the task description
+5. **Check project rules** — Read `.planr/rules.md` if it exists (MANDATORY rules)
 
-Follow the 5-phase agile development workflow:
+## Implementation Rules
 
-### Phase 1: Requirements Analysis
-1. Read existing epics in `{{agilePath}}/epics/`
-2. Break epics into features in `{{agilePath}}/features/`
-3. Create user stories with Gherkin acceptance criteria in `{{agilePath}}/stories/`
+1. **ONE subtask at a time** — implement only the target subtask
+2. **Wait for user approval** before moving to the next subtask
+3. **Follow existing patterns** — match the code style, naming conventions, and architecture from Step 4
+4. **Map to acceptance criteria** — every implementation must satisfy the Gherkin scenarios from Step 2
+5. **Update the task file** — check the box `- [x]` for completed subtasks
+6. **Don't modify unrelated code** — stay focused on the target subtask
 
-### Phase 2: Technical Design
-- Create UML sequence diagrams and C4 architecture diagrams
-- Store in `{{agilePath}}/diagrams/`
+## Agile Workflow Phases
 
-### Phase 3: Architecture Decision Records
-- Document decisions in `{{agilePath}}/adrs/`
-- Cover: functional requirements, testing strategy, non-functional requirements
+1. **Requirements Analysis** — Create epics, features, and user stories
+2. **Technical Design** — UML sequence diagrams and C4 architecture diagrams
+3. **Architecture Decisions** — ADRs for functional requirements, testing, and NFRs
+4. **Solution Planning** — Task lists and implementation management
+5. **Solution Review** — Review against acceptance criteria and refactor
 
-### Phase 4: Solution Planning
-1. Generate task lists from stories in `{{agilePath}}/tasks/`
-2. Implement one subtask at a time
-3. Wait for user approval between subtasks
-4. Update task checkboxes on completion
+## Artifact Locations
+- Task lists: `{{agilePath}}/tasks/`
+- User stories: `{{agilePath}}/stories/`
+- Gherkin acceptance criteria: `{{agilePath}}/stories/*-gherkin.feature`
+- Features: `{{agilePath}}/features/`
+- Epics: `{{agilePath}}/epics/`
+- Quick tasks: `{{agilePath}}/quick/`
+- Backlog items: `{{agilePath}}/backlog/`
+- ADRs: `{{agilePath}}/adrs/`
+- Sprints: `{{agilePath}}/sprints/`
+- Checklist: `{{agilePath}}/checklists/AGILE-DEVELOPMENT-GUIDE.md`
 
-### Phase 5: Solution Review
-- Review implementation against acceptance criteria
-- Refactor as needed
+## Frontmatter Cross-References
+Artifacts link to their parents via frontmatter fields:
+- Tasks → `storyId: "US-XXX"` or `featureId: "FEAT-XXX"`
+- Stories → `featureId: "FEAT-XXX"`
+- Features → `epicId: "EPIC-XXX"`
 
-## Rules
+Always follow these links to build the full context chain.
 
-- Always check the checklist at `{{agilePath}}/checklists/AGILE-DEVELOPMENT-GUIDE.md` for current progress
-- When creating artifacts, follow the existing naming convention: `PREFIX-NNN-slug.md`
-- Cross-reference parent/child artifacts with relative links
-- One subtask at a time during implementation
+## Naming Convention
+All artifacts follow `PREFIX-NNN-slug.md` format:
+- EPIC-001, EPIC-002, ...
+- FEAT-001, FEAT-002, ...
+- US-001, US-002, ...
+- TASK-001, TASK-002, ...
 {{#if existingEpics}}
 
 ## Current Epics

package/dist/templates/rules/codex/AGENTS.md.hbs

@@ -2,25 +2,81 @@
 
 > Generated by OpenPlanr on {{date}}
 
-## Agile Planning
-
 This project follows a structured agile workflow. All planning artifacts are in `{{agilePath}}/`.
 
-### Artifact Structure
-- Epics: `{{agilePath}}/epics/` — High-level business initiatives
-- Features: `{{agilePath}}/features/` — Capabilities derived from epics
-- User Stories: `{{agilePath}}/stories/` — User-facing requirements with Gherkin acceptance criteria
-- Tasks: `{{agilePath}}/tasks/` — Implementation task lists with checkboxes
-- ADRs: `{{agilePath}}/adrs/` — Architecture Decision Records
-
-### Workflow
-1. Check the development checklist: `{{agilePath}}/checklists/AGILE-DEVELOPMENT-GUIDE.md`
-2. Identify the current phase and next incomplete activity
-3. When implementing tasks, work on ONE subtask at a time
-4. Update task checkboxes after completing each subtask
-5. Cross-reference artifacts using relative links
-
-### Naming Convention
+## Context-Gathering Protocol
+
+Before implementing ANY task or subtask, you MUST gather full planning context by reading the artifact hierarchy. Follow this exact sequence:
+
+### Step 1: Read the Task List
+- Open the task file from `{{agilePath}}/tasks/` (e.g., `TASK-001-*.md`) or quick task from `{{agilePath}}/quick/`
+- Parse the frontmatter to find `storyId` or `featureId`
+- Identify the target subtask (first unchecked `- [ ]` item)
+- Read ALL subtasks to understand the full scope and dependencies
+
+### Step 2: Read the Parent Chain (MANDATORY)
+Follow the artifact hierarchy upward — each level adds critical context:
+
+1. **User Story** → `{{agilePath}}/stories/US-XXX-*.md`
+   - Read the full story (role, goal, benefit, acceptance criteria)
+   - Find and read the matching Gherkin file: `{{agilePath}}/stories/US-XXX-gherkin.feature`
+   - Extract the parent `featureId` from frontmatter
+
+2. **Feature** → `{{agilePath}}/features/FEAT-XXX-*.md`
+   - Read the full feature (overview, functional requirements, technical considerations)
+   - Extract the parent `epicId` from frontmatter
+
+3. **Epic** → `{{agilePath}}/epics/EPIC-XXX-*.md`
+   - Read the epic summary (business value, problem statement, success criteria)
+   - This provides the WHY behind the work
+
+### Step 3: Read Architecture Context
+- Read ALL ADRs in `{{agilePath}}/adrs/` — these are binding technical decisions
+- Check `{{agilePath}}/checklists/AGILE-DEVELOPMENT-GUIDE.md` for current progress
+
+### Step 4: Scan the Codebase
+Before writing code, understand what exists:
+
+1. **Identify the tech stack** — Read `package.json`, `tsconfig.json`, or equivalent
+2. **Scan the source tree** — List directories under `src/` (or project root)
+3. **Read architecture files** — Look for these high-priority files:
+   - Type definitions: `src/models/types.ts`, `src/types/index.ts`, or `src/types.ts`
+   - Core services: `src/services/` — understand CRUD patterns
+   - Entry point: `src/index.ts`, `src/main.ts`, or `src/app.ts` — understand registration patterns
+   - Config: `src/config.ts` or `src/services/config-service.ts`
+4. **Find related files** — Search for files matching keywords from the task description
+5. **Check project rules** — Read `.planr/rules.md` if it exists (MANDATORY rules)
+
+## Implementation Rules
+
+1. **ONE subtask at a time** — implement only the target subtask
+2. **Wait for user approval** before moving to the next subtask
+3. **Follow existing patterns** — match the code style, naming conventions, and architecture from Step 4
+4. **Map to acceptance criteria** — every implementation must satisfy the Gherkin scenarios from Step 2
+5. **Update the task file** — check the box `- [x]` for completed subtasks
+6. **Don't modify unrelated code** — stay focused on the target subtask
+
+## Artifact Locations
+- Task lists: `{{agilePath}}/tasks/`
+- User stories: `{{agilePath}}/stories/`
+- Gherkin acceptance criteria: `{{agilePath}}/stories/*-gherkin.feature`
+- Features: `{{agilePath}}/features/`
+- Epics: `{{agilePath}}/epics/`
+- Quick tasks: `{{agilePath}}/quick/`
+- Backlog items: `{{agilePath}}/backlog/`
+- ADRs: `{{agilePath}}/adrs/`
+- Sprints: `{{agilePath}}/sprints/`
+- Checklist: `{{agilePath}}/checklists/AGILE-DEVELOPMENT-GUIDE.md`
+
+## Frontmatter Cross-References
+Artifacts link to their parents via frontmatter fields:
+- Tasks → `storyId: "US-XXX"` or `featureId: "FEAT-XXX"`
+- Stories → `featureId: "FEAT-XXX"`
+- Features → `epicId: "EPIC-XXX"`
+
+Always follow these links to build the full context chain.
+
+## Naming Convention
 All artifacts follow `PREFIX-NNN-slug.md` format:
 - EPIC-001, EPIC-002, ...
 - FEAT-001, FEAT-002, ...

package/dist/templates/rules/cursor/2101-implement-task-list.mdc.hbs

@@ -1,28 +1,80 @@
 ---
-description: "Implement Task List — manage task-by-task implementation for {{projectName}}"
+description: "Implement Task List — context-aware task implementation guide for {{projectName}}"
 globs: ""
 alwaysApply: false
 ---
 
 # Implement Task List
 
-You are an implementation assistant. Guide one-task-at-a-time implementation.
+You are an implementation assistant for **{{projectName}}**. Before writing any code, you MUST gather full planning context by reading the artifact hierarchy.
 
-## Rules
+## Context-Gathering Protocol
 
-1. Only work on ONE subtask at a time
-2. Wait for user approval before moving to the next subtask
-3. After completing a subtask, update the task list by checking the box
-4. Reference acceptance criteria from the linked user story's Gherkin file
+Before implementing ANY subtask, follow this exact sequence:
 
-## Process
+### Step 1: Read the Task List
+- Open the task file from `{{agilePath}}/tasks/` (e.g., `TASK-001-*.md`)
+- Parse the frontmatter to find `storyId` or `featureId`
+- Identify the target subtask (first unchecked `- [ ]` item)
+- Read ALL subtasks to understand the full scope and dependencies
 
-1. Read the task list from `{{agilePath}}/tasks/`
-2. Find the first unchecked subtask
-3. Implement it
-4. Mark it complete in the task file
-5. Ask the user to review before proceeding
+### Step 2: Read the Parent Chain (MANDATORY)
+Follow the artifact hierarchy upward — each level adds critical context:
 
-## Task Locations
+1. **User Story** → `{{agilePath}}/stories/US-XXX-*.md`
+   - Read the full story (role, goal, benefit, acceptance criteria)
+   - Find and read the matching Gherkin file: `{{agilePath}}/stories/US-XXX-gherkin.feature`
+   - Extract the parent `featureId` from frontmatter
+
+2. **Feature** → `{{agilePath}}/features/FEAT-XXX-*.md`
+   - Read the full feature (overview, functional requirements, technical considerations)
+   - Extract the parent `epicId` from frontmatter
+
+3. **Epic** → `{{agilePath}}/epics/EPIC-XXX-*.md`
+   - Read the epic summary (business value, problem statement, success criteria)
+   - This provides the WHY behind the work
+
+### Step 3: Read Architecture Context
+- Read ALL ADRs in `{{agilePath}}/adrs/` — these are binding technical decisions
+- Check `{{agilePath}}/checklists/AGILE-DEVELOPMENT-GUIDE.md` for current progress
+
+### Step 4: Scan the Codebase
+Before writing code, understand what exists:
+
+1. **Identify the tech stack** — Read `package.json`, `tsconfig.json`, or equivalent
+2. **Scan the source tree** — List directories under `src/` (or project root)
+3. **Read architecture files** — Look for these high-priority files:
+   - Type definitions: `src/models/types.ts`, `src/types/index.ts`, or `src/types.ts`
+   - Core services: `src/services/` — understand CRUD patterns
+   - Entry point: `src/index.ts`, `src/main.ts`, or `src/app.ts` — understand registration patterns
+   - Config: `src/config.ts` or `src/services/config-service.ts`
+4. **Find related files** — Search for files matching keywords from the task description
+5. **Check project rules** — Read `.planr/rules.md` if it exists (MANDATORY rules)
+
+## Implementation Rules
+
+1. **ONE subtask at a time** — implement only the target subtask
+2. **Wait for user approval** before moving to the next subtask
+3. **Follow existing patterns** — match the code style, naming conventions, and architecture from Step 4
+4. **Map to acceptance criteria** — every implementation must satisfy the Gherkin scenarios from Step 2
+5. **Update the task file** — check the box `- [x]` for completed subtasks
+6. **Don't modify unrelated code** — stay focused on the target subtask
+
+## Artifact Locations
 - Task lists: `{{agilePath}}/tasks/`
 - User stories: `{{agilePath}}/stories/`
+- Gherkin acceptance criteria: `{{agilePath}}/stories/*-gherkin.feature`
+- Features: `{{agilePath}}/features/`
+- Epics: `{{agilePath}}/epics/`
+- Quick tasks: `{{agilePath}}/quick/`
+- Backlog items: `{{agilePath}}/backlog/`
+- ADRs: `{{agilePath}}/adrs/`
+- Sprints: `{{agilePath}}/sprints/`
+
+## Frontmatter Cross-References
+Artifacts link to their parents via frontmatter fields:
+- Tasks → `storyId: "US-XXX"` or `featureId: "FEAT-XXX"`
+- Stories → `featureId: "FEAT-XXX"`
+- Features → `epicId: "EPIC-XXX"`
+
+Always follow these links to build the full context chain.

package/dist/templates/sprints/sprint.md.hbs

@@ -0,0 +1,42 @@
+---
+id: "{{id}}"
+name: "{{name}}"
+startDate: "{{startDate}}"
+endDate: "{{endDate}}"
+duration: "{{duration}}"
+status: "{{status}}"
+created: "{{date}}"
+updated: "{{date}}"
+taskIds: [{{#each taskIds}}"{{this}}"{{#unless @last}}, {{/unless}}{{/each}}]
+---
+
+# {{id}}: {{name}}
+
+## Sprint Details
+- **Duration:** {{duration}}
+- **Start:** {{startDate}}
+- **End:** {{endDate}}
+- **Status:** {{uppercase status}}
+
+{{#if goals}}
+## Goals
+{{#each goals}}
+- {{this}}
+{{/each}}
+{{/if}}
+
+## Tasks
+{{#if taskIds}}
+{{#each taskIds}}
+- [ ] {{this}}
+{{/each}}
+{{else}}
+_No tasks assigned yet. Run `planr sprint add <taskId>` to assign tasks._
+{{/if}}
+
+## Retrospective
+_Complete this section when closing the sprint with `planr sprint close`._
+
+---
+_View progress: `planr sprint status`_
+_Close sprint: `planr sprint close`_

package/dist/templates/task-templates/api-integration.json

@@ -0,0 +1,45 @@
+{
+  "name": "api-integration",
+  "description": "External API client with retry logic, error handling, and tests",
+  "variables": ["serviceName", "baseUrl"],
+  "tasks": [
+    {
+      "id": "1.0",
+      "title": "API client setup",
+      "subtasks": [
+        { "id": "1.1", "title": "Create {{serviceName}} API client module" },
+        { "id": "1.2", "title": "Configure base URL, headers, and authentication" },
+        { "id": "1.3", "title": "Add environment variables for {{serviceName}} credentials" }
+      ]
+    },
+    {
+      "id": "2.0",
+      "title": "Implement API methods",
+      "subtasks": [
+        { "id": "2.1", "title": "Implement core API methods for {{serviceName}}" },
+        { "id": "2.2", "title": "Add request/response type definitions" },
+        { "id": "2.3", "title": "Add response parsing and data transformation" }
+      ]
+    },
+    {
+      "id": "3.0",
+      "title": "Reliability and error handling",
+      "subtasks": [
+        { "id": "3.1", "title": "Add retry logic with exponential backoff" },
+        { "id": "3.2", "title": "Add timeout configuration" },
+        { "id": "3.3", "title": "Add error classification (retryable vs fatal)" },
+        { "id": "3.4", "title": "Add rate limiting / throttling support" }
+      ]
+    },
+    {
+      "id": "4.0",
+      "title": "Testing",
+      "subtasks": [
+        { "id": "4.1", "title": "Unit tests with mocked HTTP responses" },
+        { "id": "4.2", "title": "Test retry logic and error scenarios" },
+        { "id": "4.3", "title": "Test timeout and rate limit handling" },
+        { "id": "4.4", "title": "Integration test with {{serviceName}} sandbox (if available)" }
+      ]
+    }
+  ]
+}

package/dist/templates/task-templates/auth-flow.json

@@ -0,0 +1,48 @@
+{
+  "name": "auth-flow",
+  "description": "Authentication flow with login, signup, and password reset",
+  "variables": ["authProvider"],
+  "tasks": [
+    {
+      "id": "1.0",
+      "title": "Authentication infrastructure",
+      "subtasks": [
+        { "id": "1.1", "title": "Set up {{authProvider}} authentication provider" },
+        { "id": "1.2", "title": "Configure session/token management (JWT or session)" },
+        { "id": "1.3", "title": "Add auth middleware for protected routes" }
+      ]
+    },
+    {
+      "id": "2.0",
+      "title": "Implement auth endpoints",
+      "subtasks": [
+        { "id": "2.1", "title": "POST /auth/signup — user registration" },
+        { "id": "2.2", "title": "POST /auth/login — user login" },
+        { "id": "2.3", "title": "POST /auth/logout — session termination" },
+        { "id": "2.4", "title": "POST /auth/forgot-password — password reset request" },
+        { "id": "2.5", "title": "POST /auth/reset-password — password reset confirmation" }
+      ]
+    },
+    {
+      "id": "3.0",
+      "title": "Security hardening",
+      "subtasks": [
+        { "id": "3.1", "title": "Add input validation and sanitization" },
+        { "id": "3.2", "title": "Implement rate limiting on auth endpoints" },
+        { "id": "3.3", "title": "Add password strength requirements" },
+        { "id": "3.4", "title": "Secure token storage and rotation" }
+      ]
+    },
+    {
+      "id": "4.0",
+      "title": "Testing",
+      "subtasks": [
+        { "id": "4.1", "title": "Test signup flow (valid input, duplicate email, weak password)" },
+        { "id": "4.2", "title": "Test login flow (valid credentials, invalid, locked account)" },
+        { "id": "4.3", "title": "Test password reset flow end-to-end" },
+        { "id": "4.4", "title": "Test auth middleware (valid token, expired, missing)" },
+        { "id": "4.5", "title": "Test rate limiting on auth endpoints" }
+      ]
+    }
+  ]
+}

package/dist/templates/task-templates/database-migration.json

@@ -0,0 +1,44 @@
+{
+  "name": "database-migration",
+  "description": "Schema change with migration, rollback, and seed data",
+  "variables": ["tableName", "changeDescription"],
+  "tasks": [
+    {
+      "id": "1.0",
+      "title": "Plan schema change",
+      "subtasks": [
+        { "id": "1.1", "title": "Document {{changeDescription}} for {{tableName}} table" },
+        { "id": "1.2", "title": "Review impact on existing queries and indexes" },
+        { "id": "1.3", "title": "Check for foreign key constraints and cascading effects" }
+      ]
+    },
+    {
+      "id": "2.0",
+      "title": "Create migration",
+      "subtasks": [
+        { "id": "2.1", "title": "Write up migration for {{tableName}}" },
+        { "id": "2.2", "title": "Write down migration (rollback)" },
+        { "id": "2.3", "title": "Test migration on local database" }
+      ]
+    },
+    {
+      "id": "3.0",
+      "title": "Update application code",
+      "subtasks": [
+        { "id": "3.1", "title": "Update ORM models/types for {{tableName}}" },
+        { "id": "3.2", "title": "Update queries and repository layer" },
+        { "id": "3.3", "title": "Update API serialization if schema changed" }
+      ]
+    },
+    {
+      "id": "4.0",
+      "title": "Testing and validation",
+      "subtasks": [
+        { "id": "4.1", "title": "Update seed data for {{tableName}}" },
+        { "id": "4.2", "title": "Run existing tests and fix breakages" },
+        { "id": "4.3", "title": "Test rollback migration works correctly" },
+        { "id": "4.4", "title": "Verify data integrity after migration" }
+      ]
+    }
+  ]
+}

package/dist/templates/task-templates/react-component.json

@@ -0,0 +1,45 @@
+{
+  "name": "react-component",
+  "description": "React component with stories, tests, and types",
+  "variables": ["componentName"],
+  "tasks": [
+    {
+      "id": "1.0",
+      "title": "Component setup",
+      "subtasks": [
+        { "id": "1.1", "title": "Create {{componentName}} component file with props interface" },
+        { "id": "1.2", "title": "Add component styles (CSS modules or styled-components)" },
+        { "id": "1.3", "title": "Export from component index barrel" }
+      ]
+    },
+    {
+      "id": "2.0",
+      "title": "Implement component logic",
+      "subtasks": [
+        { "id": "2.1", "title": "Implement {{componentName}} render logic and state" },
+        { "id": "2.2", "title": "Add event handlers and callbacks" },
+        { "id": "2.3", "title": "Handle loading, error, and empty states" },
+        { "id": "2.4", "title": "Add accessibility attributes (aria-labels, roles, keyboard nav)" }
+      ]
+    },
+    {
+      "id": "3.0",
+      "title": "Storybook stories",
+      "subtasks": [
+        { "id": "3.1", "title": "Create default story for {{componentName}}" },
+        { "id": "3.2", "title": "Add variant stories (sizes, states, themes)" },
+        { "id": "3.3", "title": "Add interactive story with controls" }
+      ]
+    },
+    {
+      "id": "4.0",
+      "title": "Tests",
+      "subtasks": [
+        { "id": "4.1", "title": "Unit tests for {{componentName}} rendering" },
+        { "id": "4.2", "title": "Test user interactions and event handlers" },
+        { "id": "4.3", "title": "Test edge cases and error states" },
+        { "id": "4.4", "title": "Snapshot or visual regression test" }
+      ]
+    }
+  ]
+}

package/dist/templates/task-templates/rest-endpoint.json

@@ -0,0 +1,53 @@
+{
+  "name": "rest-endpoint",
+  "description": "CRUD REST endpoint with validation, auth, tests, and docs",
+  "variables": ["entityName", "basePath"],
+  "tasks": [
+    {
+      "id": "1.0",
+      "title": "Define data model and types",
+      "subtasks": [
+        { "id": "1.1", "title": "Create {{entityName}} interface/type definition" },
+        { "id": "1.2", "title": "Add Zod validation schema for {{entityName}}" },
+        { "id": "1.3", "title": "Define request/response DTOs" }
+      ]
+    },
+    {
+      "id": "2.0",
+      "title": "Implement API routes",
+      "subtasks": [
+        { "id": "2.1", "title": "Create GET {{basePath}} — list all {{entityName}}s" },
+        { "id": "2.2", "title": "Create GET {{basePath}}/:id — get single {{entityName}}" },
+        { "id": "2.3", "title": "Create POST {{basePath}} — create {{entityName}}" },
+        { "id": "2.4", "title": "Create PUT {{basePath}}/:id — update {{entityName}}" },
+        { "id": "2.5", "title": "Create DELETE {{basePath}}/:id — delete {{entityName}}" }
+      ]
+    },
+    {
+      "id": "3.0",
+      "title": "Add middleware and validation",
+      "subtasks": [
+        { "id": "3.1", "title": "Add request body validation middleware" },
+        { "id": "3.2", "title": "Add authentication/authorization checks" },
+        { "id": "3.3", "title": "Add error handling and proper HTTP status codes" }
+      ]
+    },
+    {
+      "id": "4.0",
+      "title": "Write tests",
+      "subtasks": [
+        { "id": "4.1", "title": "Unit tests for {{entityName}} validation logic" },
+        { "id": "4.2", "title": "Integration tests for all CRUD endpoints" },
+        { "id": "4.3", "title": "Test error cases (404, 400, 401, 403)" }
+      ]
+    },
+    {
+      "id": "5.0",
+      "title": "Documentation",
+      "subtasks": [
+        { "id": "5.1", "title": "Add API documentation for {{basePath}} endpoints" },
+        { "id": "5.2", "title": "Update README with new endpoint details" }
+      ]
+    }
+  ]
+}

package/dist/templates/tasks/task-list.md.hbs

@@ -44,4 +44,4 @@ status: "pending"
 {{/if}}
 
 ## Notes
-_Mark tasks complete by checking the boxes above, or run `planr task implement {{id}}`._
+_Mark tasks complete by checking the boxes above. Use your coding agent (Claude Code, Cursor, Codex) with the generated rules for context-aware implementation._

package/dist/utils/constants.d.ts

@@ -7,6 +7,8 @@ export declare const ARTIFACT_DIRS: {
     readonly stories: "stories";
     readonly tasks: "tasks";
     readonly quick: "quick";
+    readonly backlog: "backlog";
+    readonly sprints: "sprints";
     readonly adrs: "adrs";
     readonly checklists: "checklists";
 };
@@ -16,6 +18,8 @@ export declare const ID_PREFIXES: {
     readonly story: "US";
     readonly task: "TASK";
     readonly quick: "QT";
+    readonly backlog: "BL";
+    readonly sprint: "SPRINT";
     readonly adr: "ADR";
 };
 export declare function getTemplatesDir(): string;

package/dist/utils/constants.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"constants.d.ts","sourceRoot":"","sources":["../../src/utils/constants.ts"],"names":[],"mappings":"AAMA,eAAO,MAAM,eAAe,sBAAsB,CAAC;AAEnD,eAAO,MAAM,iBAAiB,eAAe,CAAC;AAC9C,eAAO,MAAM,wBAAwB,kBAAkB,CAAC;AAExD,eAAO,MAAM,aAAa;;;;;;;;CAQhB,CAAC;AAEX,eAAO,MAAM,WAAW;;;;;;;CAOd,CAAC;AAEX,wBAAgB,eAAe,IAAI,MAAM,CAExC"}
+{"version":3,"file":"constants.d.ts","sourceRoot":"","sources":["../../src/utils/constants.ts"],"names":[],"mappings":"AAMA,eAAO,MAAM,eAAe,sBAAsB,CAAC;AAEnD,eAAO,MAAM,iBAAiB,eAAe,CAAC;AAC9C,eAAO,MAAM,wBAAwB,kBAAkB,CAAC;AAExD,eAAO,MAAM,aAAa;;;;;;;;;;CAUhB,CAAC;AAEX,eAAO,MAAM,WAAW;;;;;;;;;CASd,CAAC;AAEX,wBAAgB,eAAe,IAAI,MAAM,CAExC"}