kyro-ai 3.2.0

package/skills/sprint-forge/manifest.json

@@ -0,0 +1,165 @@
+{
+  "$schema": "https://synapsync.dev/schemas/cognitive-manifest.json",
+  "name": "sprint-forge",
+  "type": "skill",
+  "version": "2.1.0",
+  "description": "Adaptive sprint workflow with one orchestrator agent, built-in checkpoints, and slash commands — analysis, roadmap, iterative sprints, debt tracking, context persistence, and per-project learning",
+  "author": {
+    "name": "SynapSync",
+    "url": "https://github.com/SynapSync",
+    "email": "hello@synapsync.dev"
+  },
+  "license": "Apache-2.0",
+  "category": "workflow",
+  "tags": [
+    "workflow",
+    "sprint",
+    "planning",
+    "execution",
+    "debt-tracking",
+    "roadmap",
+    "iterative",
+    "adaptive",
+    "context-persistence",
+    "reentry"
+  ],
+  "providers": [
+    "claude",
+    "openai",
+    "cursor",
+    "windsurf",
+    "copilot",
+    "gemini",
+    "codex"
+  ],
+  "file": "SKILL.md",
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/SynapSync/kyro-ai"
+  },
+  "homepage": "https://github.com/SynapSync/kyro-ai",
+  "assets": {
+    "modes": 3,
+    "helpers": 4,
+    "templates": 4
+  },
+  "changelog": [
+    {
+      "version": "2.1.0",
+      "date": "2026-03-23",
+      "changes": [
+        "Replace {project-name} with {scope} in Configuration Resolution and default output_dir paths — {scope} is a kebab-case work topic (e.g., oauth-implementation, ui-redesign), not the repo name",
+        "Update INIT Step 2 config table: Project Name → Scope with clarification that repo is already {cwd}",
+        "Update architecture, getting-started, and WORKFLOW.yaml to reflect {scope} convention"
+      ]
+    },
+    {
+      "version": "2.0.0",
+      "date": "2026-03-08",
+      "changes": [
+        "Evolve from standalone skill to full workflow with one orchestrator agent, built-in checkpoints, slash commands (/kyro:forge, /kyro:status, /kyro:wrap-up), and per-project learning via persistent rules"
+      ]
+    },
+    {
+      "version": "1.10.0",
+      "date": "2026-03-07",
+      "changes": [
+        "Add checkpoint-per-phase persistence rule to SPRINT EXECUTE workflow — sprint file is written to disk after each phase completes, balancing crash safety with execution fluidity"
+      ]
+    },
+    {
+      "version": "1.9.0",
+      "date": "2026-03-06",
+      "changes": [
+        "Add YAML frontmatter properties to all templates (SPRINT, ROADMAP, PROJECT-README, REENTRY-PROMPTS) and finding file format",
+        "Add `agents` field to frontmatter — tracks AI model or agent names (e.g., gpt-5, codex, cursor, opencode) that created or modified the document",
+        "Update INIT and SPRINT modes with frontmatter generation instructions and close-time frontmatter updates"
+      ]
+    },
+    {
+      "version": "1.8.0",
+      "date": "2026-03-03",
+      "changes": [
+        "Remove obsidian integration from kyro — syncing to vault is now a separate, explicit user step"
+      ]
+    },
+    {
+      "version": "1.7.0",
+      "date": "2026-03-03",
+      "changes": [
+        "Remove AGENTS.md branded block dependency for output_kyro_dir resolution",
+        "INIT now asks user once and stores output_kyro_dir in README.md and RE-ENTRY-PROMPTS.md",
+        "SPRINT Step 0 now extracts output_kyro_dir from re-entry prompt paths as primary source",
+        "REENTRY-PROMPTS template now includes explicit output_kyro_dir section at the top",
+        "Simplified Configuration Resolution in SKILL.md to 3 clear rules"
+      ]
+    },
+    {
+      "version": "1.6.0",
+      "date": "2026-02-21",
+      "changes": [
+        "Updated Integration table with explicit obsidian skill invocation and MCP guardrail"
+      ]
+    },
+    {
+      "version": "1.5.0",
+      "date": "2026-02-21",
+      "changes": [
+        "Remove changelog from frontmatter, remove Version History section, add Asset Loading (Mode-Gated) table"
+      ]
+    },
+    {
+      "version": "1.4.0",
+      "date": "2026-02-19",
+      "changes": [
+        "Branded AGENTS.md block support — output_kyro_dir config persisted in synapsync-skills Configuration table",
+        "New output_kyro_dir config key remembered across sessions via AGENTS.md (supplements auto-discovery and re-entry prompts)"
+      ]
+    },
+    {
+      "version": "1.3.0",
+      "date": "2026-02-18",
+      "changes": [
+        "Replaced staging pattern with interactive path resolution — ask once before first write",
+        "Option 1: {cwd}/.agents/kyro/scopes/{project-name}/ (default)",
+        "Option 2: {user-root}/kyro/{project-name}/ (custom)",
+        "Removed post-production delivery steps from INIT and SPRINT modes",
+        "Added Step 0 to SPRINT and STATUS for locating {output_kyro_dir} in future sessions"
+      ]
+    },
+    {
+      "version": "1.2.0",
+      "date": "2026-02-17",
+      "changes": [
+        "Migrated to deterministic staging pattern (.agents/staging/kyro/)",
+        "Renamed {output_base} to {output_kyro_dir} for consistency across all skills",
+        "Added post-production delivery step to INIT and SPRINT modes"
+      ]
+    },
+    {
+      "version": "1.1.0",
+      "date": "2026-02-16",
+      "changes": [
+        "Add [>] carry-over task state for tasks that pass to the next sprint",
+        "Add execution metadata (date, executor) to sprint header",
+        "Add 'Converted to Phase' as disposition action for recommendations",
+        "Add Findings Consolidation phase as recommended sprint closing pattern",
+        "Add Evidence field to task format for inline documentation",
+        "Add 'New Technical Debt Detected' as fourth retro subsection"
+      ]
+    },
+    {
+      "version": "1.0.0",
+      "date": "2026-02-16",
+      "changes": [
+        "Initial release — 3 modes (INIT, SPRINT, STATUS)",
+        "Adaptive roadmap with sprint-by-sprint generation",
+        "Formal debt tracking with inheritance",
+        "Re-entry prompts for context persistence across sessions",
+        "Language-agnostic: works for any project type, language, or framework"
+      ]
+    }
+  ],
+  "createdAt": "2026-02-16T00:00:00Z",
+  "updatedAt": "2026-03-08T00:00:00Z"
+}

package/templates/split-claude-md/AGENTS.md

@@ -0,0 +1,96 @@
+# AGENTS.md — Kyro AI Rules
+
+## Sprint Discipline
+
+### One Sprint at a Time
+
+- Never start a new sprint while one is in progress.
+- Each sprint must reach a terminal state (completed, abandoned, or blocked) before the next begins.
+- If the current sprint is blocked, document the blocker and pause — do not silently start new work.
+
+### Retrospective Required
+
+- Every completed sprint MUST end with a retrospective (the retrospective phase of forge).
+- The retro captures: what worked, what did not, estimation accuracy, and concrete improvements.
+- Learnings from the retro are written to `LEARNED.md` and to `.agents/kyro/scopes/rules.md` for per-project reuse.
+- Skipping the retro is a workflow violation.
+
+### Debt is Inherited
+
+- Technical debt items from previous sprints carry forward automatically.
+- Debt items are never silently dropped. They can only be:
+  - **Resolved** — fixed and verified in a sprint task.
+  - **Deferred** — explicitly moved to a future sprint with justification.
+  - **Accepted** — acknowledged as permanent with documented rationale.
+- Debt aged beyond 3 sprints is flagged as critical.
+
+## Quality Gates
+
+Every sprint phase transition requires a quality gate:
+
+1. **Analysis gate** — Analysis phase findings reviewed and approved before planning.
+2. **Plan gate** — Sprint plan reviewed and approved before implementation.
+3. **Implementation gate** — Each task passes lint, type-check, and tests before marking complete.
+4. **Review gate** — Review step validates task output against acceptance criteria.
+5. **Commit gate** — All quality checks pass before final commit.
+
+Rules:
+- Never skip a gate. If a gate fails, fix the issue before proceeding.
+- Gate approvals require explicit user confirmation.
+- If tests or lint are not configured, note it as a warning but do not block.
+
+## Re-entry Prompt
+
+When a session ends or context is compacted:
+
+1. Save the current sprint state as a checkpoint.
+2. Write a re-entry prompt to `.agents/kyro/scopes/{project}/reentry.md` that contains:
+   - Current sprint ID and phase.
+   - Last completed task.
+   - Next task and its context.
+   - Any blockers or open questions.
+3. On session start, load the re-entry prompt to restore context.
+
+## Orchestrator Protocols
+
+### Analysis Protocol
+
+Use for: initial codebase analysis, architecture mapping, risk identification.
+
+- Read-only during this phase. Must not modify any files.
+- Runs automatically during the Analyze phase of `/kyro:forge`.
+- Can be invoked manually for ad-hoc exploration.
+
+### Review Checklist
+
+Use for: task validation, quality checklist enforcement.
+
+- Runs after each task completion.
+- Checks: correctness, test coverage, lint compliance, acceptance criteria.
+- Classifies findings as BLOCKER, WARNING, or SUGGESTION.
+- BLOCKERs must be resolved before task is marked done.
+
+### Debug Protocol
+
+Use for: root cause analysis when a task fails or tests break.
+
+- Invoked automatically on repeated failures.
+- Must produce a root cause report before suggesting a fix.
+- Fixes are proposed, not applied — user approves before changes.
+
+### Full Cycle Coordination
+
+The orchestrator manages the Analyze -> Plan -> Implement -> Review -> Commit lifecycle.
+
+- Runs analysis, review, and debug protocols as needed.
+- Enforces gate transitions and checkpoint saves.
+- Handles parallel task suggestions when worktrees are available.
+
+## General Rules
+
+- Always read the project's `CLAUDE.md` before starting work.
+- Respect the project's existing code style and conventions.
+- When uncertain about scope, ask the user rather than guessing.
+- Prefer small, focused commits over large monolithic changes.
+- Never force-push to main/master without explicit user approval.
+- Log all agent delegations for traceability.

package/templates/split-claude-md/CLAUDE.md

@@ -0,0 +1,67 @@
+# Project — CLAUDE.md
+
+## Workflow
+
+This project uses **Kyro** for structured sprint execution.
+
+- Workflow: `kyro-ai` (installed via Claude Code adapter, generic markdown setup, or local path)
+- Sprint output: `.agents/kyro/scopes/{project}/`
+- Learned rules: `.agents/kyro/scopes/rules.md`
+
+## Agent Rules
+
+See [AGENTS.md](./AGENTS.md) for:
+- Sprint discipline and quality gate requirements
+- Orchestrator protocols (analysis, review, debug)
+- Re-entry prompt conventions
+
+## Learned Rules
+
+See [LEARNED.md](./LEARNED.md) for project-specific learnings auto-populated from sprint retros.
+
+## Commands
+
+See [COMMANDS.md](./COMMANDS.md) for the full slash-command reference.
+
+## Project Conventions
+
+### Language & Framework
+
+- Language: <!-- e.g., TypeScript 5.x -->
+- Framework: <!-- e.g., Next.js 14 -->
+- Package manager: <!-- e.g., pnpm -->
+
+### Build & Test
+
+```bash
+# Install dependencies
+# npm install
+
+# Run dev server
+# npm run dev
+
+# Type-check
+# npm run typecheck
+
+# Build
+# npm run build
+
+# Tests/lint
+# Add project-specific commands here when available.
+```
+
+### Code Style
+
+- <!-- Add project-specific code style rules here -->
+
+### Directory Layout
+
+```
+src/
+  <!-- Describe your project's directory layout here -->
+```
+
+### Important Notes
+
+- <!-- Add critical project-specific notes here -->
+- <!-- e.g., "Never modify the migrations/ directory manually" -->

package/templates/split-claude-md/COMMANDS.md

@@ -0,0 +1,37 @@
+# COMMANDS.md — Kyro Command Reference
+
+## /kyro:forge
+
+Full sprint cycle: Analyze -> Plan -> Implement -> Review -> Commit.
+
+```
+/kyro:forge <project path or description>
+```
+
+Delegates to the orchestrator agent, which coordinates analysis, review,
+and debug protocols through validation gates. Each gate requires explicit
+user approval before proceeding to the next phase.
+
+## /kyro:status
+
+Project progress and technical debt summary.
+
+```
+/kyro:status                    # Full project status
+/kyro:status velocity           # Velocity chart (last 5 sprints)
+/kyro:status debt               # Debt heatmap by file/module
+```
+
+Shows completion rates, estimation accuracy, and highlights areas with
+accumulated technical debt.
+
+---
+
+## Project-Specific Overrides
+
+Add custom command behavior or aliases below. These take precedence
+over the defaults above.
+
+<!-- Example: -->
+<!-- /kyro:forge always runs with --parallel when on a feature branch -->
+<!-- /kyro:forge max tasks = 5 for this project (smaller scope) -->

package/templates/split-claude-md/LEARNED.md

@@ -0,0 +1,39 @@
+# LEARNED.md — Project-Specific Learnings
+
+This file is auto-populated by kyro-ai during sprint retrospectives.
+Do not edit manually unless correcting an error. New entries are appended
+by the learner helper after each sprint retrospective.
+
+Format: each entry includes the sprint ID, date, and a concise rule.
+
+---
+
+## Estimation
+
+<!-- Learnings about task estimation accuracy for this project -->
+<!-- Example: -->
+<!-- - [S-003 / 2025-01-15] Release validation consistently takes 2x estimated time due to environment setup. -->
+
+## Quality
+
+<!-- Learnings about code quality, testing, and review patterns -->
+<!-- Example: -->
+<!-- - [S-005 / 2025-02-01] Integration tests for the payment module must run against the staging API, not mocks. -->
+
+## Architecture
+
+<!-- Learnings about codebase structure, dependencies, and design decisions -->
+<!-- Example: -->
+<!-- - [S-002 / 2025-01-10] The auth module is tightly coupled to the user module; changes to one often require changes to the other. -->
+
+## Testing
+
+<!-- Learnings about test strategies, flaky tests, and coverage gaps -->
+<!-- Example: -->
+<!-- - [S-004 / 2025-01-20] E2E tests for the dashboard timeout on CI if run in parallel; use --runInBand. -->
+
+## Process
+
+<!-- Learnings about workflow, tooling, and team conventions -->
+<!-- Example: -->
+<!-- - [S-006 / 2025-02-10] PR reviews are faster when the description includes a screenshot for UI changes. -->

package/templates/split-claude-md/SOUL.md

@@ -0,0 +1,107 @@
+# SOUL.md — Personal Communication Style
+
+This file defines your personal preferences for how AI agents communicate and write code. It is loaded alongside CLAUDE.md to personalize the agent's behavior.
+
+Place this file in your project root or `~/.claude/` for global preferences.
+
+---
+
+## Tone
+
+<!-- Uncomment and customize the style that matches your preference -->
+
+<!-- Formal: professional, structured, complete sentences -->
+<!-- tone: formal -->
+
+<!-- Casual: conversational, contractions, direct -->
+<!-- tone: casual -->
+
+<!-- Terse: minimal words, maximum signal, no filler -->
+<!-- tone: terse -->
+
+tone: casual
+
+---
+
+## Verbosity
+
+<!-- How much detail you want in responses -->
+
+<!-- minimal: just the answer, no explanation unless asked -->
+<!-- standard: answer + brief context -->
+<!-- detailed: answer + full reasoning + alternatives -->
+
+verbosity: minimal
+
+---
+
+## Language
+
+<!-- Primary language for communication -->
+<!-- The agent will respond in this language unless you write in another -->
+
+language: en
+
+---
+
+## Code Style
+
+<!-- Your code style preferences — the agent will follow these when writing code -->
+
+```yaml
+indentation: 2 spaces
+semicolons: false          # JS/TS: omit semicolons
+quotes: single             # JS/TS: single quotes
+trailing_commas: true      # ES5 trailing commas
+naming:
+  variables: camelCase
+  functions: camelCase
+  classes: PascalCase
+  constants: UPPER_SNAKE_CASE
+  files: kebab-case
+max_line_length: 100
+```
+
+---
+
+## Response Format
+
+<!-- How you prefer responses to be structured -->
+
+```yaml
+use_headers: true           # Use markdown headers for structure
+use_bullet_points: true     # Prefer bullets over paragraphs
+code_blocks: fenced         # Always use fenced code blocks with language
+show_file_paths: true       # Show file paths before code changes
+```
+
+---
+
+## Domain Expertise
+
+<!-- What you can be assumed to know — the agent won't over-explain these topics -->
+
+```yaml
+assume_knowledge_of:
+  - git (advanced)
+  - typescript
+  - node.js ecosystem
+  - terminal / CLI usage
+  # Add your areas of expertise here
+```
+
+---
+
+## Anti-Patterns
+
+<!-- Things you explicitly don't want the agent to do -->
+
+```yaml
+never:
+  - Add emojis to code or responses
+  - Add comments that explain what code does (only why)
+  - Create README files unless asked
+  - Use verbose error messages for internal code
+  - Add type annotations that TypeScript can infer
+  # Add your pet peeves here
+```