@intentsolutionsio/sprint 1.0.0 → 1.0.3

package/skills/agent-patterns/references/examples.md

@@ -5,6 +5,7 @@
 The simplest pattern: one agent implementing one spec file with a shared contract.
 
 **SPAWN REQUEST block:**
+
 ```
 SPAWN REQUEST
 Agent: python-dev
@@ -14,6 +15,7 @@ Scope: All backend endpoints
 ```
 
 **Agent reads these files, implements, then returns:**
+
 ```
 AGENT REPORT
 Agent: python-dev
@@ -34,6 +36,7 @@ Multiple agents running concurrently, each assigned to a non-overlapping domain
 boundary to prevent file conflicts.
 
 **Architect produces three SPAWN REQUEST blocks:**
+
 ```
 SPAWN REQUEST
 Agent: python-dev
@@ -54,6 +57,7 @@ Scope: Docker, GitHub Actions, and deployment configs
 ```
 
 **Domain boundaries (no file overlap):**
+
 ```
 python-dev  → src/api/*, src/models/*, tests/api/*
 nextjs-dev  → app/*, components/*, tests/ui/*
@@ -61,6 +65,7 @@ cicd-agent  → .github/workflows/*, Dockerfile, docker-compose.yml
 ```
 
 **All three agents run simultaneously. Reports collected:**
+
 ```
 AGENT REPORT
 Agent: python-dev
@@ -90,6 +95,7 @@ Testing agents must run after implementation agents complete. QA runs first,
 then UI testing runs after QA passes.
 
 **Sequential SPAWN REQUEST chain:**
+
 ```
 SPAWN REQUEST
 Agent: qa-test-agent
@@ -106,6 +112,7 @@ Scope: Browser-based E2E tests for all user flows
 ```
 
 **QA agent report:**
+
 ```
 AGENT REPORT
 Agent: qa-test-agent
@@ -122,6 +129,7 @@ Conformity: 2 endpoints deviate from api-contract.md error codes
 ```
 
 **UI test agent report (using structured format):**
+
 ```
 AGENT REPORT
 Agent: ui-test-agent
@@ -145,6 +153,7 @@ After collecting all agent reports, the architect decides whether to iterate
 or finalize.
 
 **Architect receives reports from Iteration 1:**
+
 ```
 python-dev: COMPLETE (all endpoints working)
 nextjs-dev: COMPLETE (all components rendered)
@@ -153,6 +162,7 @@ ui-test-agent: 1 failure (checkout button disabled)
 ```
 
 **Architect analysis:**
+
 ```
 Conformity Review:
   ✓ 4/6 API endpoints fully conformant
@@ -177,6 +187,7 @@ Updated status.md:
 ```
 
 **Architect spawns narrowed Iteration 2:**
+
 ```
 SPAWN REQUEST
 Agent: python-dev
@@ -196,6 +207,7 @@ The orchestrator detects the project framework and selects appropriate
 specialized agents.
 
 **Project detection:**
+
 ```
 Phase 0 scan:
   → Found: next.config.js → Framework: Next.js
@@ -209,6 +221,7 @@ Agent selection:
 ```
 
 **For a different project stack:**
+
 ```
 Phase 0 scan:
   → Found: nuxt.config.ts → Framework: Nuxt 3
@@ -226,6 +239,7 @@ Agent selection:
 When an agent fails to produce a valid report or encounters unrecoverable errors.
 
 **Failed agent report:**
+
 ```
 AGENT REPORT
 Agent: python-dev
@@ -237,6 +251,7 @@ Conformity: Unable to assess — implementation did not start
 ```
 
 **Architect response:**
+
 ```
 Architect reviews failure:
   → Root cause: platform-specific dependency issue
@@ -256,6 +271,7 @@ Notes: Use asyncpg instead of psycopg2-binary for PostgreSQL
 When agents need strict boundaries to prevent overlapping modifications.
 
 **Tightly scoped SPAWN REQUEST:**
+
 ```
 SPAWN REQUEST
 Agent: python-dev
@@ -273,6 +289,7 @@ Forbidden Paths:
 ```
 
 **Agent respects boundaries in its report:**
+
 ```
 AGENT REPORT
 Agent: python-dev

package/skills/agent-patterns/references/ui-test-report.md

@@ -3,15 +3,18 @@
 ## UI TEST REPORT
 
 ### MODE
+
 AUTOMATED
 
 ### SUMMARY
+
 - Total tests run: 8
 - Passed: 7
 - Failed: 1
 - Session duration: 45s
 
 ### COVERAGE
+
 - Scenarios covered:
   - Login with valid credentials
   - Login with invalid password
@@ -21,6 +24,7 @@ AUTOMATED
   - Email verification flow (requires email testing setup)
 
 ### FAILURES
+
 - Scenario: Registration validation
   - Path/URL: /register
   - Symptom: Error message not displayed
@@ -28,8 +32,11 @@ AUTOMATED
   - Actual: Form submits without feedback
 
 ### CONSOLE ERRORS
+
 None.
 
 ### NOTES FOR ARCHITECT
+
 - Registration error handling needs frontend fix
-```
+
+```

package/skills/api-contract/SKILL.md

@@ -1,13 +1,21 @@
 ---
 name: api-contract
-description: |
-  Configure this skill should be used when the user asks about "API contract", "api-contract.md", "shared interface", "TypeScript interfaces", "request response schemas", "endpoint design", or needs guidance on designing contracts that coordinate backend and frontend agents. Use when building or modifying API endpoints. Trigger with phrases like 'create API', 'design endpoint', or 'API scaffold'.
+description: 'Configure this skill should be used when the user asks about "API contract",
+  "api-contract.md", "shared interface", "TypeScript interfaces", "request response
+  schemas", "endpoint design", or needs guidance on designing contracts that coordinate
+  backend and frontend agents. Use when building or modifying API endpoints. Trigger
+  with phrases like ''create API'', ''design endpoint'', or ''API scaffold''.
+
+  '
 allowed-tools: Read
 version: 1.0.0
 author: Damien Laine <damien.laine@gmail.com>
 license: MIT
-compatible-with: claude-code, codex, openclaw
-tags: [community, api, typescript]
+tags:
+- community
+- api
+- typescript
+compatibility: Designed for Claude Code, also compatible with Codex and OpenClaw
 ---
 # API Contract
 
@@ -51,6 +59,7 @@ API Contract guides the creation of `api-contract.md` files that serve as the sh
 ## Examples
 
 **Authentication endpoint contract:**
+
 ```markdown
 #### POST /auth/register
 
@@ -78,6 +87,7 @@ Create a new user account.
 ```
 
 **Paginated list endpoint:**
+
 ```markdown
 #### GET /products
 
@@ -99,6 +109,7 @@ List products with pagination.
 ```
 
 **Shared TypeScript interface:**
+
 ```typescript
 interface ApiError {
   code: string;
@@ -112,4 +123,4 @@ interface ApiError {
 - `${CLAUDE_SKILL_DIR}/references/writing-endpoints.md` -- Endpoint definition template and key elements
 - `${CLAUDE_SKILL_DIR}/references/typescript-interfaces.md` -- Canonical type definitions and guidelines
 - `${CLAUDE_SKILL_DIR}/references/pagination.md` -- Pagination parameters and PaginatedResponse interface
-- `${CLAUDE_SKILL_DIR}/references/best-practices.md` -- Contract authoring rules (specificity, DRY, no implementation details)
+- `${CLAUDE_SKILL_DIR}/references/best-practices.md` -- Contract authoring rules (specificity, DRY, no implementation details)

package/skills/api-contract/references/best-practices.md

@@ -22,6 +22,7 @@
   "password": "SecurePass123"
 }
 ```
+
 ```
 
 ### Document All States
@@ -42,6 +43,7 @@ Reference shared types instead of duplicating:
 ### No Implementation Details
 
 The contract defines WHAT, not HOW:
+
 - Don't mention database columns
 - Don't specify frameworks
-- Don't include file paths
+- Don't include file paths

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

@@ -1,4 +1,4 @@
-# Error Handling Reference
+## Error Handling Reference
 
 ### Standard Error Format
 

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