@intentsolutionsio/sprint 1.0.0 → 1.0.6

package/skills/api-contract/references/examples.md

@@ -132,7 +132,9 @@ List products with pagination and filtering.
 ```
 
 **Errors:**
+
 - 400: Invalid query parameter → `{ code: "INVALID_PARAM", details: { limit: ["max 100"] } }`
+
 ```
 
 ## Example 2: Authentication Contract with Token Flow
@@ -183,22 +185,25 @@ Create a new user account and return authentication tokens.
 ```
 
 **Errors:**
+
 - 400: Invalid email format or weak password → field-level details
 - 409: Email already registered → `{ code: "EMAIL_EXISTS" }`
 
 ---
 
-#### POST /auth/login
+### POST /auth/login
 
 Authenticate with email and password.
 
 **Request:**
+
 | Field    | Type   | Required |
 |----------|--------|----------|
 | email    | string | yes      |
 | password | string | yes      |
 
 **Response (200 OK):**
+
 ```json
 {
   "user": UserProfile,
@@ -207,6 +212,7 @@ Authenticate with email and password.
 ```
 
 **Errors:**
+
 - 401: Invalid credentials → `{ code: "INVALID_CREDENTIALS" }`
   (same message for wrong email and wrong password to prevent enumeration)
 - 429: Too many attempts → `{ code: "RATE_LIMITED", message: "Try again in 60s" }`
@@ -219,11 +225,13 @@ Exchange a valid refresh token for new tokens. The old refresh token is
 invalidated (rotation).
 
 **Request:**
+
 | Field        | Type   | Required |
 |--------------|--------|----------|
 | refreshToken | string | yes      |
 
 **Response (200 OK):**
+
 ```json
 {
   "tokens": AuthTokens
@@ -231,6 +239,7 @@ invalidated (rotation).
 ```
 
 **Errors:**
+
 - 401: Invalid or expired refresh token → `{ code: "INVALID_REFRESH_TOKEN" }`
   (also triggered if token was already rotated — potential theft detection)
 
@@ -241,11 +250,13 @@ invalidated (rotation).
 Invalidate the refresh token for the current session.
 
 **Headers:**
+
 | Header        | Value                |
 |---------------|----------------------|
 | Authorization | Bearer {accessToken} |
 
 **Request:**
+
 | Field        | Type   | Required |
 |--------------|--------|----------|
 | refreshToken | string | yes      |
@@ -254,7 +265,9 @@ Invalidate the refresh token for the current session.
 Empty body.
 
 **Errors:**
+
 - 401: Missing or invalid access token
+
 ```
 
 ## Example 3: TypeScript Interface Definitions
@@ -408,8 +421,10 @@ List line items for a specific order.
 ```
 
 **Errors:**
+
 - 403: Order belongs to a different user
 - 404: Order not found
+
 ```
 
 ## Example 5: Contract Section for Webhook Callbacks

package/skills/api-contract/references/pagination.md

@@ -29,6 +29,7 @@ List products with pagination.
   }
 }
 ```
+
 ```
 
 ### Pagination Interface
@@ -43,4 +44,4 @@ interface PaginatedResponse<T> {
     totalPages: number;
   };
 }
-```
+```

package/skills/api-contract/references/typescript-interfaces.md

@@ -35,6 +35,7 @@ interface ApiError {
   details?: Record<string, string[]>;
 }
 ```
+
 ```
 
 ### Type Guidelines
@@ -43,4 +44,4 @@ interface ApiError {
 - Mark optional fields with `?`
 - Use union types for nullable: `string | null`
 - Include all possible response shapes
-- Match types to JSON serialization
+- Match types to JSON serialization

package/skills/api-contract/references/writing-endpoints.md

@@ -19,6 +19,7 @@ Create a new user account.
 ```
 
 **Response (201):**
+
 ```json
 {
   "id": "uuid",
@@ -29,9 +30,11 @@ Create a new user account.
 ```
 
 **Errors:**
+
 - 400: Invalid request body
 - 409: Email already exists
 - 422: Validation failed
+
 ```
 
 ### Key Elements
@@ -42,4 +45,4 @@ Create a new user account.
 | Description | What the endpoint does |
 | Request | Input schema with types and constraints |
 | Response | Output schema with status code |
-| Errors | Possible error responses |
+| Errors | Possible error responses |

package/skills/spec-writing/SKILL.md

@@ -1,13 +1,20 @@
 ---
 name: spec-writing
-description: |
-  Execute this skill should be used when the user asks about "writing specs", "specs.md format", "how to write specifications", "sprint requirements", "testing configuration", "scope definition", or needs guidance on creating effective sprint specifications for agentic development. Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.
+description: 'Execute this skill should be used when the user asks about "writing
+  specs", "specs.md format", "how to write specifications", "sprint requirements",
+  "testing configuration", "scope definition", or needs guidance on creating effective
+  sprint specifications for agentic development. Use when appropriate context detected.
+  Trigger with relevant phrases based on skill purpose.
+
+  '
 allowed-tools: Read
 version: 1.0.0
 author: Damien Laine <damien.laine@gmail.com>
 license: MIT
-compatible-with: claude-code, codex, openclaw
-tags: [community, spec-writing]
+tags:
+- community
+- spec-writing
+compatibility: Designed for Claude Code, also compatible with Codex and OpenClaw
 ---
 # Spec Writing
 
@@ -55,6 +62,7 @@ Spec Writing provides guidance on authoring effective `specs.md` files that driv
 ## Examples
 
 **Minimal but effective spec:**
+
 ```markdown
 # Sprint 1: User Authentication
 
@@ -80,6 +88,7 @@ Add user authentication with email/password login
 ```
 
 **Frontend-only sprint (no QA needed):**
+
 ```markdown
 # Sprint 3: Dashboard Redesign
 
@@ -107,4 +116,4 @@ Redesign the admin dashboard with responsive layout
 
 - `${CLAUDE_SKILL_DIR}/references/testing-configuration.md` -- Testing section options with guidance on when to use each setting
 - Sprint workflow skill for understanding how specs feed into the phase lifecycle
-- API contract skill for designing endpoint contracts referenced by specs
+- API contract skill for designing endpoint contracts referenced by specs

package/skills/spec-writing/references/examples.md

@@ -35,6 +35,7 @@ Add email/password authentication with JWT tokens and refresh token rotation.
 ```
 
 **Why this works:**
+
 - Goal is one sentence describing the deliverable
 - In Scope lists every endpoint with its behavior
 - Out of Scope prevents agent drift toward OAuth or email flows
@@ -74,6 +75,7 @@ Add dark mode with system preference detection and manual toggle.
 ```
 
 **Why manual testing is appropriate here:**
+
 - Visual correctness (contrast, readability) requires human eyes
 - Theme transitions need subjective quality assessment
 - System preference detection needs OS-level interaction
@@ -121,6 +123,7 @@ Full-text product search with type-ahead suggestions and faceted filtering.
 ```
 
 **Why this works:**
+
 - Scope is partitioned by domain (Backend / Frontend / Shared)
 - Each agent gets a clear boundary
 - Shared types are called out so both agents reference the same contract
@@ -132,6 +135,7 @@ A spec that has been narrowed based on iteration 1 results. Completed items
 are removed and only remaining work and fixes are listed.
 
 **Original specs.md (before sprint):**
+
 ```markdown
 # Sprint 2: User Dashboard
 
@@ -157,6 +161,7 @@ Build a user dashboard showing recent activity, notifications, and account setti
 ```
 
 **Updated specs.md (after iteration 1, 2 items remaining):**
+
 ```markdown
 # Sprint 2: User Dashboard (Iteration 2)
 
@@ -186,6 +191,7 @@ Fix remaining issues from iteration 1.
 ```
 
 **Why iterative narrowing matters:**
+
 - Removes completed work so agents do not re-implement it
 - Explicitly describes the two bugs with expected vs actual behavior
 - "Completed" section tells agents what NOT to touch
@@ -266,6 +272,7 @@ Real-time chat for project collaboration with channel support and presence track
 ```
 
 **Why constraints are valuable:**
+
 - Prevents agents from choosing a different WebSocket library
 - Ensures new code integrates with existing database stack
 - Manual UI testing because real-time interactions are hard to automate reliably

package/skills/spec-writing/references/testing-configuration.md

@@ -15,26 +15,31 @@ The Testing section controls which testing agents run.
 ### When to Use Each
 
 **QA: required**
+
 - New API endpoints
 - Business logic changes
 - Data validation rules
 
 **QA: skip**
+
 - Frontend-only changes
 - Documentation updates
 - Configuration changes
 
 **UI Testing: required**
+
 - User-facing features
 - Form submissions
 - Navigation flows
 
 **UI Testing Mode: manual**
+
 - Complex interactions
 - Visual verification needed
 - Exploratory testing
 
 **UI Testing Mode: automated**
+
 - Regression testing
 - Standard CRUD flows
-- Repeatable scenarios
+- Repeatable scenarios

package/skills/sprint-workflow/SKILL.md

@@ -1,13 +1,21 @@
 ---
 name: sprint-workflow
-description: |
-  Execute this skill should be used when the user asks about "how sprints work", "sprint phases", "iteration workflow", "convergent development", "sprint lifecycle", "when to use sprints", or wants to understand the sprint execution model and its convergent diffusion approach. Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.
+description: 'Execute this skill should be used when the user asks about "how sprints
+  work", "sprint phases", "iteration workflow", "convergent development", "sprint
+  lifecycle", "when to use sprints", or wants to understand the sprint execution model
+  and its convergent diffusion approach. Use when appropriate context detected. Trigger
+  with relevant phrases based on skill purpose.
+
+  '
 allowed-tools: Read
 version: 1.0.0
 author: Damien Laine <damien.laine@gmail.com>
 license: MIT
-compatible-with: claude-code, codex, openclaw
-tags: [community, workflow, sprint-workflow]
+tags:
+- community
+- workflow
+- sprint-workflow
+compatibility: Designed for Claude Code, also compatible with Codex and OpenClaw
 ---
 # Sprint Workflow
 
@@ -53,6 +61,7 @@ Sprint Workflow describes the convergent diffusion execution model used by the S
 ## Examples
 
 **Starting a new sprint:**
+
 ```bash
 /sprint:new       # Creates .claude/sprint/1/specs.md
 # Edit specs.md with requirements
@@ -60,6 +69,7 @@ Sprint Workflow describes the convergent diffusion execution model used by the S
 ```
 
 **Resuming after iteration pause:**
+
 ```bash
 # Review .claude/sprint/1/status.md for blockers
 # Adjust specs.md to narrow scope or fix conflicts
@@ -67,6 +77,7 @@ Sprint Workflow describes the convergent diffusion execution model used by the S
 ```
 
 **Typical convergence flow:**
+
 ```
 Iteration 1: Architect plans → 3 agents implement → tests find 2 failures
 Iteration 2: Architect narrows specs to 2 fixes → agents patch → tests pass
@@ -78,4 +89,4 @@ Iteration 3: All specs satisfied → FINALIZE
 - `${CLAUDE_SKILL_DIR}/references/sprint-phases.md` -- Detailed reference for all six phases with agent assignments and handoff rules
 - Agent patterns skill for SPAWN REQUEST format and report structure
 - Spec writing skill for authoring effective `specs.md` files
-- API contract skill for designing the shared interface between agents
+- API contract skill for designing the shared interface between agents

package/skills/sprint-workflow/references/examples.md

@@ -6,12 +6,14 @@ A complete sprint building a user management API with CRUD endpoints, database
 integration, and automated testing.
 
 **Step 1 — Create the sprint and write specs:**
+
 ```bash
 /sprint:new
 # Creates .claude/sprint/1/specs.md
 ```
 
 **Step 2 — Edit specs.md:**
+
 ```markdown
 # Sprint 1: User Management API
 
@@ -41,11 +43,13 @@ Build a REST API for user management with CRUD operations and role-based access.
 ```
 
 **Step 3 — Execute the sprint:**
+
 ```bash
 /sprint
 ```
 
 **Phase 0 — Load Specifications:**
+
 ```
 Orchestrator reads .claude/sprint/1/specs.md
   → Goal: User Management API (5 endpoints)
@@ -55,6 +59,7 @@ Orchestrator reads .claude/sprint/1/specs.md
 ```
 
 **Phase 1 — Architectural Planning:**
+
 ```
 project-architect reads:
   → .claude/project-map.md (existing codebase structure)
@@ -73,6 +78,7 @@ Architect returns SPAWN REQUEST blocks:
 ```
 
 **Phase 2 — Implementation (Iteration 1):**
+
 ```
 python-dev agent:
   → Reads backend-specs.md and api-contract.md
@@ -90,6 +96,7 @@ Conformity: All 5 endpoints implemented per contract
 ```
 
 **Phase 3 — Testing (Iteration 1):**
+
 ```
 qa-test-agent runs:
   → pytest tests/test_users.py
@@ -107,6 +114,7 @@ Failures:
 ```
 
 **Phase 4 — Review (Iteration 1):**
+
 ```
 Architect reviews QA report:
   → 2 failures identified
@@ -119,6 +127,7 @@ Architect reviews QA report:
 ```
 
 **Iteration 2 — Fix and Re-test:**
+
 ```
 python-dev agent:
   → Reads narrowed backend-specs.md (only 2 fixes)
@@ -136,6 +145,7 @@ Architect reviews:
 ```
 
 **Phase 5 — Finalization:**
+
 ```
 Orchestrator writes final status.md:
   Sprint 1: COMPLETE
@@ -152,6 +162,7 @@ FINALIZE
 A sprint that hit the 5-iteration limit and requires manual intervention.
 
 **status.md after 5 iterations:**
+
 ```markdown
 # Sprint 2 Status
 
@@ -172,6 +183,7 @@ of in-memory state. This is an architectural change beyond the current specs.
 ```
 
 **Manual intervention:**
+
 ```bash
 # Review the status
 cat .claude/sprint/2/status.md
@@ -196,6 +208,7 @@ A sprint focused on UI changes where automated E2E tests are impractical
 and manual visual verification is needed.
 
 **specs.md:**
+
 ```markdown
 # Sprint 3: Dashboard Redesign
 
@@ -221,6 +234,7 @@ Redesign the admin dashboard with responsive layout and dark mode support.
 ```
 
 **Sprint execution:**
+
 ```
 Phase 1: Architect produces frontend-specs.md only (no backend)
 Phase 2: nextjs-dev agent implements layout, dark mode, drag-and-drop
@@ -248,6 +262,7 @@ A sprint where backend and frontend agents work simultaneously on the same featu
 coordinated through a shared API contract.
 
 **specs.md:**
+
 ```markdown
 # Sprint 4: Product Search
 
@@ -274,6 +289,7 @@ Full-text search for products with type-ahead suggestions and faceted filtering.
 ```
 
 **Phase 2 — Parallel agent spawns:**
+
 ```
 SPAWN REQUEST
 Agent: python-dev
@@ -301,6 +317,7 @@ No file path overlap → safe for parallel execution
 ```
 
 **Phase 3 — Sequential testing:**
+
 ```
 1. qa-test-agent runs first:
    → Tests search API returns correct results

package/skills/sprint-workflow/references/sprint-phases.md

@@ -7,6 +7,7 @@ A sprint executes through 6 distinct phases:
 ### Phase 0: Load Specifications
 
 Parse the sprint directory and prepare context:
+
 - Locate sprint directory (`.claude/sprint/[N]/`)
 - Read `specs.md` for user requirements
 - Read `status.md` if resuming
@@ -15,6 +16,7 @@ Parse the sprint directory and prepare context:
 ### Phase 1: Architectural Planning
 
 The project-architect agent analyzes requirements:
+
 - Read existing `project-map.md` for architecture context
 - Read `project-goals.md` for business objectives
 - Create specification files (`api-contract.md`, `backend-specs.md`, etc.)
@@ -23,6 +25,7 @@ The project-architect agent analyzes requirements:
 ### Phase 2: Implementation
 
 Spawn implementation agents in parallel:
+
 - `python-dev` for Python/FastAPI backend
 - `nextjs-dev` for Next.js frontend
 - `cicd-agent` for CI/CD pipelines
@@ -32,6 +35,7 @@ Spawn implementation agents in parallel:
 ### Phase 3: Testing
 
 Execute testing agents:
+
 - `qa-test-agent` runs first (API and unit tests)
 - `ui-test-agent` runs after (browser-based E2E tests)
 - Framework-specific diagnostics agents run in parallel with UI tests
@@ -40,6 +44,7 @@ Execute testing agents:
 ### Phase 4: Review & Iteration
 
 Architect reviews all reports:
+
 - Analyze conformity status
 - Update specifications (remove completed, add fixes)
 - Update `status.md` with current state
@@ -48,7 +53,8 @@ Architect reviews all reports:
 ### Phase 5: Finalization
 
 Sprint completion:
+
 - Final `status.md` summary
 - All specs in consistent state
 - **Clean up manual-test-report.md** (no longer relevant)
-- Signal FINALIZE to orchestrator
+- Signal FINALIZE to orchestrator