@vpxa/aikit 0.1.1 → 0.1.2

package/scaffold/definitions/tools.mjs

@@ -5,7 +5,7 @@
  * `ide` — IDE-native tool permissions, keyed by role. Each IDE adapter
  *          maps these to its own format (e.g., Copilot tool identifiers).
  *
- * When KB adds/removes a tool, update `kb` here — all agents pick it up.
+ * When AI Kit adds/removes a tool, update `kb` here — all agents pick it up.
  *
  * NOTE: The copilot adapter currently uses `aikit/*` wildcard instead
  * of listing individual tools. This array is kept as a reference and for future

package/scaffold/flows/aikit-advanced/skills/execute/SKILL.md

@@ -1,124 +1,124 @@
----
-name: execute
-description: Implement all tasks from the task breakdown, dispatching agents in parallel where possible.
----
-
-# Execution
-
-## Purpose
-
-Execute all tasks from the breakdown, dispatching implementation agents in batches for maximum parallelism while maintaining correctness.
-
-## Inputs
-
-- `.spec/<slug>/tasks.md` — the atomic task list with dependencies and agent assignments
-
-## Process
-
-1. **Load tasks** — Read task graph, dependencies, and parallelism map
-2. **Execute by batch** — For each batch in the parallelism map:
-   a. Dispatch assigned agents in parallel (different files = safe parallelism)
-   b. Each agent receives: task scope, affected files, acceptance criteria, relevant code context via `compact()`/`digest()`
-   c. Wait for all agents in batch to complete
-   d. Run `check({})` + `test_run({})` after each batch
-   e. Fix any failures before proceeding to next batch
-3. **Track progress** — Update task checkboxes as each completes
-4. **Handle failures** — If an agent reports `BLOCKED` or `NEEDS_CONTEXT`:
-   - Max 2 retries per task with refined context
-   - If still blocked, escalate to user
-5. **Final validation** — After all batches: `check({})` + `test_run({})` must pass
-
-## Outputs
-
-Produce `.spec/<slug>/progress.md` with:
-
-```markdown
-# Execution Progress: <feature title>
-
-## Task Status
-- [x] T1.1: <description> — DONE
-- [x] T1.2: <description> — DONE
-- [x] T2.1: <description> — DONE
-- [ ] T2.2: <description> — IN PROGRESS
-...
-
-## Changes Made
-| File | Change | Task |
-|------|--------|------|
-| <file> | <description> | T1.1 |
-| ... | ... | ... |
-
-## Tests Added/Modified
-<list of test files and what they cover>
-
-## Validation
-- check: PASS/FAIL
-- test_run: PASS/FAIL (<N> passed, <M> failed)
-
-## Deviations
-<any changes from the task plan and why>
-
-## Blocked Items
-<items that needed user intervention, if any>
-```
-
-## Agents
-
-| Agent | Role |
-|-------|------|
-| **Orchestrator** | Coordinates batch execution, handles failures and retries |
-| **Implementer** | Primary code writer for backend, logic, and infrastructure tasks |
-| **Frontend** | UI/UX implementation for React components, styling, responsive design |
-| **Refactor** | Code cleanup, restructuring, and pattern alignment tasks |
-
-**Parallelism rules**:
-- Read-only agents: unlimited parallelism
-- File-modifying agents: parallel ONLY on completely different files
-- Max 4 concurrent file-modifying agents
-
-## Foundation Integration
-
-Load these skills BEFORE executing this step:
-
-| Skill | Purpose | When |
-|-------|---------|------|
-| `aikit` | Core MCP tools — search, analyze, remember, validate | Always (auto-loaded) |
-| `present` | Rich rendering for any structured output — assessments, reports, comparisons, reviews, status boards, tables, charts, and all artifact content | Use for ANY output that benefits from rich rendering, not just dashboards |
-| `multi-agents-development` | Dispatch templates, task decomposition, review pipeline patterns | Before dispatching any subagent |
-| `brainstorming` | Structured ideation for design/creative decisions | Before any design choice or new feature exploration |
-
-### Presentation Rules
-- Use `present` for **any output** that benefits from rich rendering — not limited to dashboards
-- Assessments, reports, comparisons, reviews, status boards → `present({ format: "html" })`
-- Tables, charts, progress tracking, code review findings → always present
-- Artifact content and summaries → present with structured layout
-- Only use plain text for brief confirmations and simple questions
-
-### Orchestrator Dispatch Protocol
-
-Follow the `multi-agents-development` skill patterns for dispatch:
-
-1. **Independence Check** before parallelizing:
-   - Same files? → sequential
-   - Shared mutable state? → sequential
-   - Execution-order dependent? → sequential
-   - Need shared new types? → define contract first, then parallel
-   - All clear? → **parallel dispatch**
-
-2. **Subagent Context Template** (each dispatch includes):
-   - **Scope**: exact files + boundary (do NOT touch)
-   - **Goal**: acceptance criteria, testable
-   - **Arch Context**: actual code snippets via `compact()`/`digest()`
-   - **Constraints**: patterns, conventions, anti-patterns
-   - **Self-Review**: checklist before declaring DONE
-
-3. **Status Protocol**: `DONE` | `DONE_WITH_CONCERNS` | `NEEDS_CONTEXT` | `BLOCKED`
-4. **Max 2 retries** per task — then escalate to user
-
-## Completion Criteria
-
-- [ ] All tasks marked completed
-- [ ] `check({})` passes
-- [ ] `test_run({})` passes
-- [ ] No blocked items remaining
-- [ ] `.spec/<slug>/progress.md` written
+---
+name: execute
+description: Implement all tasks from the task breakdown, dispatching agents in parallel where possible.
+---
+
+# Execution
+
+## Purpose
+
+Execute all tasks from the breakdown, dispatching implementation agents in batches for maximum parallelism while maintaining correctness.
+
+## Inputs
+
+- `.spec/<slug>/tasks.md` — the atomic task list with dependencies and agent assignments
+
+## Process
+
+1. **Load tasks** — Read task graph, dependencies, and parallelism map
+2. **Execute by batch** — For each batch in the parallelism map:
+   a. Dispatch assigned agents in parallel (different files = safe parallelism)
+   b. Each agent receives: task scope, affected files, acceptance criteria, relevant code context via `compact()`/`digest()`
+   c. Wait for all agents in batch to complete
+   d. Run `check({})` + `test_run({})` after each batch
+   e. Fix any failures before proceeding to next batch
+3. **Track progress** — Update task checkboxes as each completes
+4. **Handle failures** — If an agent reports `BLOCKED` or `NEEDS_CONTEXT`:
+   - Max 2 retries per task with refined context
+   - If still blocked, escalate to user
+5. **Final validation** — After all batches: `check({})` + `test_run({})` must pass
+
+## Outputs
+
+Produce `.spec/<slug>/progress.md` with:
+
+```markdown
+# Execution Progress: <feature title>
+
+## Task Status
+- [x] T1.1: <description> — DONE
+- [x] T1.2: <description> — DONE
+- [x] T2.1: <description> — DONE
+- [ ] T2.2: <description> — IN PROGRESS
+...
+
+## Changes Made
+| File | Change | Task |
+|------|--------|------|
+| <file> | <description> | T1.1 |
+| ... | ... | ... |
+
+## Tests Added/Modified
+<list of test files and what they cover>
+
+## Validation
+- check: PASS/FAIL
+- test_run: PASS/FAIL (<N> passed, <M> failed)
+
+## Deviations
+<any changes from the task plan and why>
+
+## Blocked Items
+<items that needed user intervention, if any>
+```
+
+## Agents
+
+| Agent | Role |
+|-------|------|
+| **Orchestrator** | Coordinates batch execution, handles failures and retries |
+| **Implementer** | Primary code writer for backend, logic, and infrastructure tasks |
+| **Frontend** | UI/UX implementation for React components, styling, responsive design |
+| **Refactor** | Code cleanup, restructuring, and pattern alignment tasks |
+
+**Parallelism rules**:
+- Read-only agents: unlimited parallelism
+- File-modifying agents: parallel ONLY on completely different files
+- Max 4 concurrent file-modifying agents
+
+## Foundation Integration
+
+Load these skills BEFORE executing this step:
+
+| Skill | Purpose | When |
+|-------|---------|------|
+| `aikit` | Core MCP tools — search, analyze, remember, validate | Always (auto-loaded) |
+| `present` | Rich rendering for any structured output — assessments, reports, comparisons, reviews, status boards, tables, charts, and all artifact content | Use for ANY output that benefits from rich rendering, not just dashboards |
+| `multi-agents-development` | Dispatch templates, task decomposition, review pipeline patterns | Before dispatching any subagent |
+| `brainstorming` | Structured ideation for design/creative decisions | Before any design choice or new feature exploration |
+
+### Presentation Rules
+- Use `present` for **any output** that benefits from rich rendering — not limited to dashboards
+- Assessments, reports, comparisons, reviews, status boards → `present({ format: "html" })`
+- Tables, charts, progress tracking, code review findings → always present
+- Artifact content and summaries → present with structured layout
+- Only use plain text for brief confirmations and simple questions
+
+### Orchestrator Dispatch Protocol
+
+Follow the `multi-agents-development` skill patterns for dispatch:
+
+1. **Independence Check** before parallelizing:
+   - Same files? → sequential
+   - Shared mutable state? → sequential
+   - Execution-order dependent? → sequential
+   - Need shared new types? → define contract first, then parallel
+   - All clear? → **parallel dispatch**
+
+2. **Subagent Context Template** (each dispatch includes):
+   - **Scope**: exact files + boundary (do NOT touch)
+   - **Goal**: acceptance criteria, testable
+   - **Arch Context**: actual code snippets via `compact()`/`digest()`
+   - **Constraints**: patterns, conventions, anti-patterns
+   - **Self-Review**: checklist before declaring DONE
+
+3. **Status Protocol**: `DONE` | `DONE_WITH_CONCERNS` | `NEEDS_CONTEXT` | `BLOCKED`
+4. **Max 2 retries** per task — then escalate to user
+
+## Completion Criteria
+
+- [ ] All tasks marked completed
+- [ ] `check({})` passes
+- [ ] `test_run({})` passes
+- [ ] No blocked items remaining
+- [ ] `.spec/<slug>/progress.md` written

package/scaffold/flows/aikit-advanced/skills/plan/SKILL.md

@@ -1,100 +1,100 @@
----
-name: plan
-description: Analyze the codebase, design the architecture, and create a detailed implementation plan.
----
-
-# Planning
-
-## Purpose
-
-Translate the specification into a concrete, phased implementation plan with architecture decisions, file-level scope, and dependency ordering.
-
-## Inputs
-
-- `.spec/<slug>/spec.md` — the validated specification
-
-## Process
-
-1. **Load spec** — Read and internalize all requirements and acceptance criteria
-2. **Codebase analysis** — `scope_map({ task: "<feature>" })` to identify affected subsystems
-3. **Deep dive** — `file_summary()` + `compact()` on each affected module
-4. **Architecture design** — Decide on:
-   - Where new code lives (new files vs extensions)
-   - API surface changes
-   - Data model changes
-   - Integration patterns
-5. **ADR for non-trivial decisions** — Use `adr-skill` for decisions that affect future development
-6. **Phase decomposition** — Break work into 3–10 ordered phases, each independently testable
-7. **Dependency graph** — Map which phases depend on others and which can parallelize
-8. **Risk assessment** — Identify implementation risks per phase
-
-## Outputs
-
-Produce `.spec/<slug>/plan.md` with:
-
-```markdown
-# Implementation Plan: <feature title>
-
-## Architecture Overview
-<high-level design with rationale>
-
-## Affected Modules
-| Module | Changes | Risk |
-|--------|---------|------|
-| <module> | <what changes> | low/medium/high |
-
-## Phases
-### Phase 1: <name>
-- **Files**: <list>
-- **Changes**: <description>
-- **Tests**: <what to test>
-- **Depends on**: none
-- **Parallelizable with**: Phase 2
-
-### Phase 2: <name>
-...
-
-## Architecture Decisions
-- ADR-<N>: <title> — <chosen option and rationale>
-
-## Risks
-| Risk | Likelihood | Impact | Mitigation |
-|------|-----------|--------|------------|
-| <risk> | low/medium/high | <impact> | <mitigation> |
-```
-
-## Agents
-
-| Agent | Role |
-|-------|------|
-| **Planner** | Creates comprehensive TDD implementation plans with phase decomposition |
-| **Explorer** | Rapid codebase exploration for discovery of affected files and dependencies |
-
-Use Explorer for initial breadth (file discovery, dependency tracing), then Planner for depth (phase design, ordering).
-
-## Foundation Integration
-
-Load these skills BEFORE executing this step:
-
-| Skill | Purpose | When |
-|-------|---------|------|
-| `aikit` | Core MCP tools — search, analyze, remember, validate | Always (auto-loaded) |
-| `present` | Rich rendering for any structured output — assessments, reports, comparisons, reviews, status boards, tables, charts, and all artifact content | Use for ANY output that benefits from rich rendering, not just dashboards |
-| `multi-agents-development` | Dispatch templates, task decomposition, review pipeline patterns | Before dispatching any subagent |
-| `brainstorming` | Structured ideation for design/creative decisions | Before any design choice or new feature exploration |
-
-### Presentation Rules
-- Use `present` for **any output** that benefits from rich rendering — not limited to dashboards
-- Assessments, reports, comparisons, reviews, status boards → `present({ format: "html" })`
-- Tables, charts, progress tracking, code review findings → always present
-- Artifact content and summaries → present with structured layout
-- Only use plain text for brief confirmations and simple questions
-
-## Completion Criteria
-
-- [ ] All spec requirements have corresponding plan phases
-- [ ] Each phase has explicit file scope and test strategy
-- [ ] Architecture decisions documented with rationale
-- [ ] Dependency graph has no circular dependencies
-- [ ] Risks identified with mitigations
-- [ ] `.spec/<slug>/plan.md` written
+---
+name: plan
+description: Analyze the codebase, design the architecture, and create a detailed implementation plan.
+---
+
+# Planning
+
+## Purpose
+
+Translate the specification into a concrete, phased implementation plan with architecture decisions, file-level scope, and dependency ordering.
+
+## Inputs
+
+- `.spec/<slug>/spec.md` — the validated specification
+
+## Process
+
+1. **Load spec** — Read and internalize all requirements and acceptance criteria
+2. **Codebase analysis** — `scope_map({ task: "<feature>" })` to identify affected subsystems
+3. **Deep dive** — `file_summary()` + `compact()` on each affected module
+4. **Architecture design** — Decide on:
+   - Where new code lives (new files vs extensions)
+   - API surface changes
+   - Data model changes
+   - Integration patterns
+5. **ADR for non-trivial decisions** — Use `adr-skill` for decisions that affect future development
+6. **Phase decomposition** — Break work into 3–10 ordered phases, each independently testable
+7. **Dependency graph** — Map which phases depend on others and which can parallelize
+8. **Risk assessment** — Identify implementation risks per phase
+
+## Outputs
+
+Produce `.spec/<slug>/plan.md` with:
+
+```markdown
+# Implementation Plan: <feature title>
+
+## Architecture Overview
+<high-level design with rationale>
+
+## Affected Modules
+| Module | Changes | Risk |
+|--------|---------|------|
+| <module> | <what changes> | low/medium/high |
+
+## Phases
+### Phase 1: <name>
+- **Files**: <list>
+- **Changes**: <description>
+- **Tests**: <what to test>
+- **Depends on**: none
+- **Parallelizable with**: Phase 2
+
+### Phase 2: <name>
+...
+
+## Architecture Decisions
+- ADR-<N>: <title> — <chosen option and rationale>
+
+## Risks
+| Risk | Likelihood | Impact | Mitigation |
+|------|-----------|--------|------------|
+| <risk> | low/medium/high | <impact> | <mitigation> |
+```
+
+## Agents
+
+| Agent | Role |
+|-------|------|
+| **Planner** | Creates comprehensive TDD implementation plans with phase decomposition |
+| **Explorer** | Rapid codebase exploration for discovery of affected files and dependencies |
+
+Use Explorer for initial breadth (file discovery, dependency tracing), then Planner for depth (phase design, ordering).
+
+## Foundation Integration
+
+Load these skills BEFORE executing this step:
+
+| Skill | Purpose | When |
+|-------|---------|------|
+| `aikit` | Core MCP tools — search, analyze, remember, validate | Always (auto-loaded) |
+| `present` | Rich rendering for any structured output — assessments, reports, comparisons, reviews, status boards, tables, charts, and all artifact content | Use for ANY output that benefits from rich rendering, not just dashboards |
+| `multi-agents-development` | Dispatch templates, task decomposition, review pipeline patterns | Before dispatching any subagent |
+| `brainstorming` | Structured ideation for design/creative decisions | Before any design choice or new feature exploration |
+
+### Presentation Rules
+- Use `present` for **any output** that benefits from rich rendering — not limited to dashboards
+- Assessments, reports, comparisons, reviews, status boards → `present({ format: "html" })`
+- Tables, charts, progress tracking, code review findings → always present
+- Artifact content and summaries → present with structured layout
+- Only use plain text for brief confirmations and simple questions
+
+## Completion Criteria
+
+- [ ] All spec requirements have corresponding plan phases
+- [ ] Each phase has explicit file scope and test strategy
+- [ ] Architecture decisions documented with rationale
+- [ ] Dependency graph has no circular dependencies
+- [ ] Risks identified with mitigations
+- [ ] `.spec/<slug>/plan.md` written

package/scaffold/flows/aikit-advanced/skills/spec/SKILL.md

@@ -1,100 +1,100 @@
----
-name: spec
-description: Elicit requirements, clarify scope, and define acceptance criteria through structured dialogue.
----
-
-# Specification
-
-## Purpose
-
-Transform a vague or broad feature request into a precise, testable specification through requirements elicitation and stakeholder dialogue.
-
-## Inputs
-
-- User's feature request, issue, or idea
-- Codebase context (accessed via aikit MCP tools)
-
-## Process
-
-1. **Understand intent** — Parse what the user wants and why
-2. **Search for context** — `search()` for related prior decisions, existing patterns, and similar features
-3. **Elicit requirements** — Ask structured questions to clarify:
-   - **Functional**: What must the system do?
-   - **Non-functional**: Performance, security, accessibility constraints
-   - **Scope boundaries**: What is explicitly out of scope?
-   - **Acceptance criteria**: How do we know it's done?
-4. **Score clarity** — Use the `requirements-clarity` skill to score 0–100. Iterate questions until ≥ 90.
-5. **Draft specification** — Write formal spec with all requirements resolved
-
-## Outputs
-
-Produce `.spec/<slug>/spec.md` with:
-
-```markdown
-# Specification: <feature title>
-
-## Summary
-<1-2 sentence description>
-
-## Motivation
-<why this feature is needed>
-
-## Functional Requirements
-1. <requirement with acceptance criterion>
-2. ...
-
-## Non-Functional Requirements
-- Performance: <constraints>
-- Security: <constraints>
-- Accessibility: <constraints>
-
-## Scope
-### In Scope
-- <item>
-
-### Out of Scope
-- <item>
-
-## Acceptance Criteria
-- [ ] <testable criterion>
-- [ ] ...
-
-## Open Questions
-<none — all resolved during elicitation>
-
-## Clarity Score: <N>/100
-```
-
-## Agents
-
-| Agent | Role |
-|-------|------|
-| **Researcher-Alpha** | Deep analysis of existing codebase patterns, prior decisions, and technical constraints |
-
-Use the `brainstorming` skill for creative/design exploration before formalizing requirements. Use `requirements-clarity` skill to score and iterate until the spec is unambiguous.
-
-## Foundation Integration
-
-Load these skills BEFORE executing this step:
-
-| Skill | Purpose | When |
-|-------|---------|------|
-| `aikit` | Core MCP tools — search, analyze, remember, validate | Always (auto-loaded) |
-| `present` | Rich rendering for any structured output — assessments, reports, comparisons, reviews, status boards, tables, charts, and all artifact content | Use for ANY output that benefits from rich rendering, not just dashboards |
-| `multi-agents-development` | Dispatch templates, task decomposition, review pipeline patterns | Before dispatching any subagent |
-| `brainstorming` | Structured ideation for design/creative decisions | Before any design choice or new feature exploration |
-
-### Presentation Rules
-- Use `present` for **any output** that benefits from rich rendering — not limited to dashboards
-- Assessments, reports, comparisons, reviews, status boards → `present({ format: "html" })`
-- Tables, charts, progress tracking, code review findings → always present
-- Artifact content and summaries → present with structured layout
-- Only use plain text for brief confirmations and simple questions
-
-## Completion Criteria
-
-- [ ] All functional requirements have acceptance criteria
-- [ ] Scope boundaries are explicit
-- [ ] Requirements clarity score ≥ 90
-- [ ] No open questions remain
-- [ ] `.spec/<slug>/spec.md` written
+---
+name: spec
+description: Elicit requirements, clarify scope, and define acceptance criteria through structured dialogue.
+---
+
+# Specification
+
+## Purpose
+
+Transform a vague or broad feature request into a precise, testable specification through requirements elicitation and stakeholder dialogue.
+
+## Inputs
+
+- User's feature request, issue, or idea
+- Codebase context (accessed via aikit MCP tools)
+
+## Process
+
+1. **Understand intent** — Parse what the user wants and why
+2. **Search for context** — `search()` for related prior decisions, existing patterns, and similar features
+3. **Elicit requirements** — Ask structured questions to clarify:
+   - **Functional**: What must the system do?
+   - **Non-functional**: Performance, security, accessibility constraints
+   - **Scope boundaries**: What is explicitly out of scope?
+   - **Acceptance criteria**: How do we know it's done?
+4. **Score clarity** — Use the `requirements-clarity` skill to score 0–100. Iterate questions until ≥ 90.
+5. **Draft specification** — Write formal spec with all requirements resolved
+
+## Outputs
+
+Produce `.spec/<slug>/spec.md` with:
+
+```markdown
+# Specification: <feature title>
+
+## Summary
+<1-2 sentence description>
+
+## Motivation
+<why this feature is needed>
+
+## Functional Requirements
+1. <requirement with acceptance criterion>
+2. ...
+
+## Non-Functional Requirements
+- Performance: <constraints>
+- Security: <constraints>
+- Accessibility: <constraints>
+
+## Scope
+### In Scope
+- <item>
+
+### Out of Scope
+- <item>
+
+## Acceptance Criteria
+- [ ] <testable criterion>
+- [ ] ...
+
+## Open Questions
+<none — all resolved during elicitation>
+
+## Clarity Score: <N>/100
+```
+
+## Agents
+
+| Agent | Role |
+|-------|------|
+| **Researcher-Alpha** | Deep analysis of existing codebase patterns, prior decisions, and technical constraints |
+
+Use the `brainstorming` skill for creative/design exploration before formalizing requirements. Use `requirements-clarity` skill to score and iterate until the spec is unambiguous.
+
+## Foundation Integration
+
+Load these skills BEFORE executing this step:
+
+| Skill | Purpose | When |
+|-------|---------|------|
+| `aikit` | Core MCP tools — search, analyze, remember, validate | Always (auto-loaded) |
+| `present` | Rich rendering for any structured output — assessments, reports, comparisons, reviews, status boards, tables, charts, and all artifact content | Use for ANY output that benefits from rich rendering, not just dashboards |
+| `multi-agents-development` | Dispatch templates, task decomposition, review pipeline patterns | Before dispatching any subagent |
+| `brainstorming` | Structured ideation for design/creative decisions | Before any design choice or new feature exploration |
+
+### Presentation Rules
+- Use `present` for **any output** that benefits from rich rendering — not limited to dashboards
+- Assessments, reports, comparisons, reviews, status boards → `present({ format: "html" })`
+- Tables, charts, progress tracking, code review findings → always present
+- Artifact content and summaries → present with structured layout
+- Only use plain text for brief confirmations and simple questions
+
+## Completion Criteria
+
+- [ ] All functional requirements have acceptance criteria
+- [ ] Scope boundaries are explicit
+- [ ] Requirements clarity score ≥ 90
+- [ ] No open questions remain
+- [ ] `.spec/<slug>/spec.md` written