@vpxa/aikit 0.1.1 → 0.1.2

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

@@ -1,99 +1,99 @@
----
-name: task
-description: Break the implementation plan into ordered, atomic tasks with dependencies and agent assignments.
----
-
-# Task Breakdown
-
-## Purpose
-
-Decompose the implementation plan into small, atomic tasks that agents can execute independently, with clear dependency ordering and acceptance criteria per task.
-
-## Inputs
-
-- `.spec/<slug>/plan.md` — the phased implementation plan
-
-## Process
-
-1. **Load plan** — Read phases, file scope, and dependency graph
-2. **Decompose phases into tasks** — Each task should:
-   - Touch 1–3 files maximum
-   - Have a single, testable outcome
-   - Take one agent one focused session
-3. **Define dependencies** — Map task-to-task dependencies (not just phase-to-phase)
-4. **Assign agents** — Match each task to the best-fit agent based on scope
-5. **Identify parallelism** — Mark which tasks can run simultaneously
-6. **Architecture review** — Have Architect-Reviewer validate task ordering won't create integration issues
-
-## Outputs
-
-Produce `.spec/<slug>/tasks.md` with:
-
-```markdown
-# Task Breakdown: <feature title>
-
-## Task Graph
-
-### Phase 1: <name>
-- [ ] **T1.1**: <description>
-  - Files: <list>
-  - Agent: <agent name>
-  - Depends on: none
-  - Acceptance: <testable criterion>
-
-- [ ] **T1.2**: <description>
-  - Files: <list>
-  - Agent: <agent name>
-  - Depends on: T1.1
-  - Acceptance: <testable criterion>
-
-### Phase 2: <name>
-- [ ] **T2.1**: <description> (can parallel with T1.2)
-  ...
-
-## Parallelism Map
-| Batch | Tasks | Agents |
-|-------|-------|--------|
-| 1 | T1.1 | Implementer |
-| 2 | T1.2, T2.1 | Implementer, Frontend |
-| 3 | T2.2 | Implementer |
-| ... | ... | ... |
-
-## Estimated Batches: <N>
-```
-
-## Agents
-
-| Agent | Role |
-|-------|------|
-| **Planner** | Decomposes plan phases into atomic tasks with dependency ordering |
-| **Architect-Reviewer-Alpha** | Validates task decomposition won't cause integration issues |
-
-Planner does the decomposition, then Architect-Reviewer validates the task graph.
-
-## 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
-
-- [ ] Every plan phase maps to ≥1 task
-- [ ] Each task touches ≤3 files
-- [ ] Dependencies form a DAG (no cycles)
-- [ ] Parallelism opportunities identified
-- [ ] Architect review confirms no integration risks
-- [ ] `.spec/<slug>/tasks.md` written
+---
+name: task
+description: Break the implementation plan into ordered, atomic tasks with dependencies and agent assignments.
+---
+
+# Task Breakdown
+
+## Purpose
+
+Decompose the implementation plan into small, atomic tasks that agents can execute independently, with clear dependency ordering and acceptance criteria per task.
+
+## Inputs
+
+- `.spec/<slug>/plan.md` — the phased implementation plan
+
+## Process
+
+1. **Load plan** — Read phases, file scope, and dependency graph
+2. **Decompose phases into tasks** — Each task should:
+   - Touch 1–3 files maximum
+   - Have a single, testable outcome
+   - Take one agent one focused session
+3. **Define dependencies** — Map task-to-task dependencies (not just phase-to-phase)
+4. **Assign agents** — Match each task to the best-fit agent based on scope
+5. **Identify parallelism** — Mark which tasks can run simultaneously
+6. **Architecture review** — Have Architect-Reviewer validate task ordering won't create integration issues
+
+## Outputs
+
+Produce `.spec/<slug>/tasks.md` with:
+
+```markdown
+# Task Breakdown: <feature title>
+
+## Task Graph
+
+### Phase 1: <name>
+- [ ] **T1.1**: <description>
+  - Files: <list>
+  - Agent: <agent name>
+  - Depends on: none
+  - Acceptance: <testable criterion>
+
+- [ ] **T1.2**: <description>
+  - Files: <list>
+  - Agent: <agent name>
+  - Depends on: T1.1
+  - Acceptance: <testable criterion>
+
+### Phase 2: <name>
+- [ ] **T2.1**: <description> (can parallel with T1.2)
+  ...
+
+## Parallelism Map
+| Batch | Tasks | Agents |
+|-------|-------|--------|
+| 1 | T1.1 | Implementer |
+| 2 | T1.2, T2.1 | Implementer, Frontend |
+| 3 | T2.2 | Implementer |
+| ... | ... | ... |
+
+## Estimated Batches: <N>
+```
+
+## Agents
+
+| Agent | Role |
+|-------|------|
+| **Planner** | Decomposes plan phases into atomic tasks with dependency ordering |
+| **Architect-Reviewer-Alpha** | Validates task decomposition won't cause integration issues |
+
+Planner does the decomposition, then Architect-Reviewer validates the task graph.
+
+## 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
+
+- [ ] Every plan phase maps to ≥1 task
+- [ ] Each task touches ≤3 files
+- [ ] Dependencies form a DAG (no cycles)
+- [ ] Parallelism opportunities identified
+- [ ] Architect review confirms no integration risks
+- [ ] `.spec/<slug>/tasks.md` written

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

@@ -1,122 +1,122 @@
----
-name: verify
-description: Dual code review, architecture review, security review, and comprehensive test validation.
----
-
-# Verification (Advanced)
-
-## Purpose
-
-Perform thorough multi-perspective validation of all changes through parallel dual code review, architecture review, and security analysis.
-
-## Inputs
-
-- `.spec/<slug>/spec.md` — original requirements and acceptance criteria
-- `.spec/<slug>/plan.md` — architecture decisions and phase design
-- `.spec/<slug>/tasks.md` — task breakdown with per-task acceptance criteria
-- `.spec/<slug>/progress.md` — implementation status and changes made
-
-## Process
-
-1. **Load all artifacts** — Read spec, plan, tasks, and progress
-2. **Dual code review** (parallel):
-   - Code-Reviewer-Alpha: focus on correctness, conventions, quality
-   - Code-Reviewer-Beta: focus on edge cases, error handling, maintainability
-3. **Architecture review** (parallel with code review):
-   - Architect-Reviewer-Alpha: validate changes align with plan and ADRs
-   - Architect-Reviewer-Beta: assess long-term maintainability and evolution
-4. **Security review**:
-   - Security agent: OWASP Top 10, auth/authz, input validation, secrets
-5. **Quality gates** — `check({})` + `test_run({})` must pass
-6. **Blast radius** — `blast_radius({ changed_files: [...] })` on all modified files
-7. **Acceptance criteria** — Verify each spec acceptance criterion is met
-8. **FORGE gate** — `evidence_map({ action: "gate" })` for final quality assessment
-9. **Synthesize report** — Merge all reviewer findings into unified verdict
-
-## Outputs
-
-Produce `.spec/<slug>/verify-report.md` with:
-
-```markdown
-# Verification Report: <feature title>
-
-## Verdict: PASS | FAIL
-
-## Acceptance Criteria
-- [x] <criterion> — verified by <method>
-- [ ] <criterion> — FAILED: <reason>
-
-## Quality Gates
-- check: PASS/FAIL
-- test_run: PASS/FAIL (<N> passed, <M> failed)
-- blast_radius: <impact summary>
-- FORGE gate: YIELD/HOLD/HARD_BLOCK
-
-## Code Review (Alpha)
-<findings with severity: critical/major/minor/suggestion>
-
-## Code Review (Beta)
-<findings with severity>
-
-## Architecture Review
-<alignment assessment, any concerns>
-
-## Security Review
-<vulnerabilities found, OWASP compliance>
-
-## Recommendation
-APPROVE | REQUEST CHANGES
-
-### Required Changes (if any)
-1. <change needed>
-2. ...
-```
-
-## Agents
-
-| Agent | Role |
-|-------|------|
-| **Code-Reviewer-Alpha** | Primary code review — correctness, quality, conventions |
-| **Code-Reviewer-Beta** | Secondary code review — edge cases, error handling, maintainability |
-| **Architect-Reviewer-Alpha** | Primary architecture review — alignment with plan and ADRs |
-| **Architect-Reviewer-Beta** | Secondary architecture review — long-term evolution |
-| **Security** | Security analysis — OWASP, auth, input validation |
-
-**Parallelism**: All 5 reviewers can run in parallel — they are read-only.
-
-## 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
-
-### FORGE Quality Gate
-
-After all reviews complete:
-1. `evidence_map({ action: "gate", task_id: "<slug>" })` → returns YIELD/HOLD/HARD_BLOCK
-2. YIELD → approved, proceed to commit
-3. HOLD → minor issues, fix then re-gate (max 3 rounds)
-4. HARD_BLOCK → critical issues, escalate to user
-
-## Completion Criteria
-
-- [ ] Dual code review complete (2 reviewers)
-- [ ] Architecture review complete (2 reviewers)
-- [ ] Security review complete
-- [ ] `check({})` passes
-- [ ] `test_run({})` passes
-- [ ] All spec acceptance criteria verified
-- [ ] FORGE gate passed (YIELD)
-- [ ] `.spec/<slug>/verify-report.md` written with clear verdict
+---
+name: verify
+description: Dual code review, architecture review, security review, and comprehensive test validation.
+---
+
+# Verification (Advanced)
+
+## Purpose
+
+Perform thorough multi-perspective validation of all changes through parallel dual code review, architecture review, and security analysis.
+
+## Inputs
+
+- `.spec/<slug>/spec.md` — original requirements and acceptance criteria
+- `.spec/<slug>/plan.md` — architecture decisions and phase design
+- `.spec/<slug>/tasks.md` — task breakdown with per-task acceptance criteria
+- `.spec/<slug>/progress.md` — implementation status and changes made
+
+## Process
+
+1. **Load all artifacts** — Read spec, plan, tasks, and progress
+2. **Dual code review** (parallel):
+   - Code-Reviewer-Alpha: focus on correctness, conventions, quality
+   - Code-Reviewer-Beta: focus on edge cases, error handling, maintainability
+3. **Architecture review** (parallel with code review):
+   - Architect-Reviewer-Alpha: validate changes align with plan and ADRs
+   - Architect-Reviewer-Beta: assess long-term maintainability and evolution
+4. **Security review**:
+   - Security agent: OWASP Top 10, auth/authz, input validation, secrets
+5. **Quality gates** — `check({})` + `test_run({})` must pass
+6. **Blast radius** — `blast_radius({ changed_files: [...] })` on all modified files
+7. **Acceptance criteria** — Verify each spec acceptance criterion is met
+8. **FORGE gate** — `evidence_map({ action: "gate" })` for final quality assessment
+9. **Synthesize report** — Merge all reviewer findings into unified verdict
+
+## Outputs
+
+Produce `.spec/<slug>/verify-report.md` with:
+
+```markdown
+# Verification Report: <feature title>
+
+## Verdict: PASS | FAIL
+
+## Acceptance Criteria
+- [x] <criterion> — verified by <method>
+- [ ] <criterion> — FAILED: <reason>
+
+## Quality Gates
+- check: PASS/FAIL
+- test_run: PASS/FAIL (<N> passed, <M> failed)
+- blast_radius: <impact summary>
+- FORGE gate: YIELD/HOLD/HARD_BLOCK
+
+## Code Review (Alpha)
+<findings with severity: critical/major/minor/suggestion>
+
+## Code Review (Beta)
+<findings with severity>
+
+## Architecture Review
+<alignment assessment, any concerns>
+
+## Security Review
+<vulnerabilities found, OWASP compliance>
+
+## Recommendation
+APPROVE | REQUEST CHANGES
+
+### Required Changes (if any)
+1. <change needed>
+2. ...
+```
+
+## Agents
+
+| Agent | Role |
+|-------|------|
+| **Code-Reviewer-Alpha** | Primary code review — correctness, quality, conventions |
+| **Code-Reviewer-Beta** | Secondary code review — edge cases, error handling, maintainability |
+| **Architect-Reviewer-Alpha** | Primary architecture review — alignment with plan and ADRs |
+| **Architect-Reviewer-Beta** | Secondary architecture review — long-term evolution |
+| **Security** | Security analysis — OWASP, auth, input validation |
+
+**Parallelism**: All 5 reviewers can run in parallel — they are read-only.
+
+## 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
+
+### FORGE Quality Gate
+
+After all reviews complete:
+1. `evidence_map({ action: "gate", task_id: "<slug>" })` → returns YIELD/HOLD/HARD_BLOCK
+2. YIELD → approved, proceed to commit
+3. HOLD → minor issues, fix then re-gate (max 3 rounds)
+4. HARD_BLOCK → critical issues, escalate to user
+
+## Completion Criteria
+
+- [ ] Dual code review complete (2 reviewers)
+- [ ] Architecture review complete (2 reviewers)
+- [ ] Security review complete
+- [ ] `check({})` passes
+- [ ] `test_run({})` passes
+- [ ] All spec acceptance criteria verified
+- [ ] FORGE gate passed (YIELD)
+- [ ] `.spec/<slug>/verify-report.md` written with clear verdict

package/scaffold/flows/aikit-basic/skills/assess/SKILL.md

@@ -1,82 +1,82 @@
----
-name: assess
-description: Understand scope, analyze the codebase, and identify the implementation approach.
----
-
-# Assessment
-
-## Purpose
-
-Analyze the task requirements and codebase to produce a clear, actionable assessment before any code changes begin.
-
-## Inputs
-
-- User's task description or issue reference
-- Codebase (accessed via aikit MCP tools)
-
-## Process
-
-1. **Parse the goal** — Extract what needs to change, success criteria, and constraints
-2. **Search for prior work** — `search({ query: "<task keywords>" })` to check for existing decisions or related code
-3. **Map affected scope** — `scope_map({ task: "<description>" })` to identify files and modules involved
-4. **Analyze structure** — `file_summary()` on each affected file; `compact()` for deeper sections
-5. **Identify risks** — Note dependencies, breaking change potential, test coverage gaps
-6. **Draft approach** — Outline the implementation strategy in 3–7 steps
-
-## Outputs
-
-Produce `.spec/<slug>/assessment.md` with:
-
-```markdown
-# Assessment: <task title>
-
-## Goal
-<what needs to happen>
-
-## Affected Files
-<list of files with brief reason>
-
-## Approach
-<numbered implementation steps>
-
-## Risks
-<potential issues and mitigations>
-
-## Open Questions
-<anything that needs clarification before proceeding>
-```
-
-## Agents
-
-| Agent | Role |
-|-------|------|
-| **Explorer** | Rapid file discovery, dependency tracing, structural context |
-| **Researcher-Alpha** | Deep analysis of complex logic, prior decisions, architectural implications |
-
-Use Explorer first for breadth, then Researcher-Alpha for depth on complex areas.
-
-## 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 affected files identified
-- [ ] Implementation approach is concrete (not vague)
-- [ ] Risks documented with mitigations
-- [ ] No unresolved open questions that block implementation
-- [ ] `.spec/<slug>/assessment.md` written
+---
+name: assess
+description: Understand scope, analyze the codebase, and identify the implementation approach.
+---
+
+# Assessment
+
+## Purpose
+
+Analyze the task requirements and codebase to produce a clear, actionable assessment before any code changes begin.
+
+## Inputs
+
+- User's task description or issue reference
+- Codebase (accessed via aikit MCP tools)
+
+## Process
+
+1. **Parse the goal** — Extract what needs to change, success criteria, and constraints
+2. **Search for prior work** — `search({ query: "<task keywords>" })` to check for existing decisions or related code
+3. **Map affected scope** — `scope_map({ task: "<description>" })` to identify files and modules involved
+4. **Analyze structure** — `file_summary()` on each affected file; `compact()` for deeper sections
+5. **Identify risks** — Note dependencies, breaking change potential, test coverage gaps
+6. **Draft approach** — Outline the implementation strategy in 3–7 steps
+
+## Outputs
+
+Produce `.spec/<slug>/assessment.md` with:
+
+```markdown
+# Assessment: <task title>
+
+## Goal
+<what needs to happen>
+
+## Affected Files
+<list of files with brief reason>
+
+## Approach
+<numbered implementation steps>
+
+## Risks
+<potential issues and mitigations>
+
+## Open Questions
+<anything that needs clarification before proceeding>
+```
+
+## Agents
+
+| Agent | Role |
+|-------|------|
+| **Explorer** | Rapid file discovery, dependency tracing, structural context |
+| **Researcher-Alpha** | Deep analysis of complex logic, prior decisions, architectural implications |
+
+Use Explorer first for breadth, then Researcher-Alpha for depth on complex areas.
+
+## 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 affected files identified
+- [ ] Implementation approach is concrete (not vague)
+- [ ] Risks documented with mitigations
+- [ ] No unresolved open questions that block implementation
+- [ ] `.spec/<slug>/assessment.md` written