@vpxa/aikit 0.1.1 → 0.1.3

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

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

@@ -1,105 +1,105 @@
----
-name: implement
-description: Write code following the assessment plan, using TDD practices where applicable.
----
-
-# Implementation
-
-## Purpose
-
-Execute the implementation plan from the assessment, writing production code and tests.
-
-## Inputs
-
-- `.spec/<slug>/assessment.md` — the approach, affected files, and risks
-
-## Process
-
-1. **Read assessment** — Load `.spec/<slug>/assessment.md` and internalize the approach
-2. **Set up tests first** — Where applicable, write failing tests that define success
-3. **Implement changes** — Follow the approach steps sequentially
-   - One logical change per commit-worthy chunk
-   - Stay within the assessed file scope — do not expand without re-assessment
-4. **Run validation** — `check({})` for type/lint errors, `test_run({})` for test results
-5. **Fix issues** — Iterate until `check` and `test_run` pass (max 3 rounds)
-6. **Document progress** — Write progress artifact with what was done and any deviations
-
-## Outputs
-
-Produce `.spec/<slug>/progress.md` with:
-
-```markdown
-# Implementation Progress: <task title>
-
-## Changes Made
-<list of files changed with brief description>
-
-## Tests
-<tests added or modified>
-
-## Deviations from Assessment
-<any changes to the original plan and why>
-
-## Validation
-- check: PASS/FAIL
-- test_run: PASS/FAIL (<N> passed, <M> failed)
-
-## Notes
-<anything the reviewer should know>
-```
-
-## Agents
-
-| Agent | Role |
-|-------|------|
-| **Implementer** | Primary code writer — follows TDD, writes production code and tests |
-| **Frontend** | UI/UX specialist — use when changes involve React components, styling, or responsive design |
-
-Dispatch Implementer for backend/logic changes, Frontend for UI changes. Both can run in parallel if working on different files.
-
-## 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 assessment steps implemented
-- [ ] `check({})` passes (no type/lint errors)
-- [ ] `test_run({})` passes (no test failures)
-- [ ] No files modified outside assessed scope
-- [ ] `.spec/<slug>/progress.md` written
+---
+name: implement
+description: Write code following the assessment plan, using TDD practices where applicable.
+---
+
+# Implementation
+
+## Purpose
+
+Execute the implementation plan from the assessment, writing production code and tests.
+
+## Inputs
+
+- `.spec/<slug>/assessment.md` — the approach, affected files, and risks
+
+## Process
+
+1. **Read assessment** — Load `.spec/<slug>/assessment.md` and internalize the approach
+2. **Set up tests first** — Where applicable, write failing tests that define success
+3. **Implement changes** — Follow the approach steps sequentially
+   - One logical change per commit-worthy chunk
+   - Stay within the assessed file scope — do not expand without re-assessment
+4. **Run validation** — `check({})` for type/lint errors, `test_run({})` for test results
+5. **Fix issues** — Iterate until `check` and `test_run` pass (max 3 rounds)
+6. **Document progress** — Write progress artifact with what was done and any deviations
+
+## Outputs
+
+Produce `.spec/<slug>/progress.md` with:
+
+```markdown
+# Implementation Progress: <task title>
+
+## Changes Made
+<list of files changed with brief description>
+
+## Tests
+<tests added or modified>
+
+## Deviations from Assessment
+<any changes to the original plan and why>
+
+## Validation
+- check: PASS/FAIL
+- test_run: PASS/FAIL (<N> passed, <M> failed)
+
+## Notes
+<anything the reviewer should know>
+```
+
+## Agents
+
+| Agent | Role |
+|-------|------|
+| **Implementer** | Primary code writer — follows TDD, writes production code and tests |
+| **Frontend** | UI/UX specialist — use when changes involve React components, styling, or responsive design |
+
+Dispatch Implementer for backend/logic changes, Frontend for UI changes. Both can run in parallel if working on different files.
+
+## 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 assessment steps implemented
+- [ ] `check({})` passes (no type/lint errors)
+- [ ] `test_run({})` passes (no test failures)
+- [ ] No files modified outside assessed scope
+- [ ] `.spec/<slug>/progress.md` written