@vpxa/aikit 0.1.86 → 0.1.88

package/scaffold/claude-code/commands/aikit-flow-create.md

@@ -1,79 +0,0 @@
-# aikit flow-create
-
-> Create a new flow from scratch or migrate an existing workflow to aikit format
-
-## Flow Creation Assistant
-
-Create a new development flow or migrate an existing workflow to the aikit flow format.
-
-### Mode 1: Create from Scratch
-
-Guide the user through building a complete flow:
-
-1. **Define the workflow** — Ask what the flow should accomplish (e.g., "TDD workflow", "documentation pipeline", "migration process")
-2. **Design steps** — Break the workflow into sequential steps (3-8 is ideal)
-3. **For each step**:
-   - Define the step id, name, and description
-   - Write the instruction (README.md content — what the agent should do)
-   - Identify what it produces (output artifacts)
-   - Identify what it requires (which previous steps must complete first)
-   - Optionally assign preferred agents
-4. **Generate flow.json** — Create the manifest with all steps
-5. **Write step READMEs** — Create instruction files for each step
-6. **Install** — Use `flow_add` to install from the local directory
-
-### Mode 2: Migrate Existing Workflow
-
-If the user has an existing workflow (scripts, docs, runbooks) that they want to convert:
-
-1. **Analyze the source** — Read the existing workflow files to understand the process
-2. **Map to steps** — Identify discrete steps with clear inputs/outputs
-3. **Identify gaps** — What's missing for a complete flow? (instructions? ordering? agents?)
-4. **Fill gaps with user** — Ask user to clarify any ambiguous parts
-5. **Generate the flow** — Create flow.json + step READMEs
-6. **Install and validate** — Use `flow_add` and `flow_info` to verify
-
-### Flow Structure
-
-```
-my-flow/
-  flow.json              — Flow manifest (name, version, steps, agents)
-  steps/
-    step-1/
-      README.md          — Step instructions (what the agent should do)
-    step-2/
-      README.md
-      references/        — Optional reference files for the step
-    ...
-```
-
-### flow.json Format
-```json
-{
-  "name": "my-flow",
-  "version": "1.0.0",
-  "description": "What this flow does",
-  "steps": [
-    {
-      "id": "step-id",
-      "name": "Human-readable Step Name",
-      "instruction": "steps/step-id/README.md",
-      "produces": ["artifact-name.md"],
-      "requires": [],
-      "agents": ["Preferred-Agent"],
-      "description": "Brief description of this step"
-    }
-  ],
-  "agents": [],
-  "artifacts_dir": ".spec",
-  "install": []
-}
-```
-
-### Step README Format
-Each step README should include:
-- **Goal** — What this step accomplishes
-- **Inputs** — What context/artifacts from prior steps are needed
-- **Instructions** — Detailed steps for the agent to follow
-- **Output** — What artifact(s) to produce and where to save them
-- **Acceptance criteria** — How to know the step is complete

package/scaffold/claude-code/commands/aikit-flow-manage.md

@@ -1,23 +0,0 @@
-# aikit flow-manage
-
-> List, inspect, update, and remove installed flows
-
-## Flow Management
-
-Manage your installed development flows.
-
-### Available Actions
-
-1. **List flows** — `flow_list` to see all installed flows with status
-2. **Inspect a flow** — `flow_info` to see detailed steps, agents, and artifacts
-3. **Check status** — `flow_status` to see the active flow and current step
-4. **Update a flow** — `flow_update` to pull latest changes for git-installed flows
-5. **Remove a flow** — `flow_remove` to uninstall (builtin flows cannot be removed)
-6. **Start a flow** — `flow_start` to begin executing a flow
-7. **Reset active flow** — `flow_reset` to clear active flow state
-
-### Workflow
-1. If no specific action requested, start with `flow_list` and present overview
-2. Use `present` to display flow information in a clear table/card format
-3. For updates, warn if there's an active flow that might be affected
-4. For removals, confirm with user before proceeding

package/scaffold/claude-code/commands/aikit-implement.md

@@ -1,16 +0,0 @@
-# aikit implement
-
-> Full lifecycle implementation: plan → build → review → commit
-
-## Implementation Pipeline
-
-Follow the Orchestrator's full workflow:
-
-1. **Phase 0: Design Gate** — Orchestrator checks if design is needed. Creative/additive work triggers brainstorming first. Use `/design` if you want to start with design explicitly.
-2. **Phase 1: Planning** — Research, draft plan, present to user for approval
-3. **Phase 2: Implementation** — Execute phases in parallel batches
-4. **Phase 3: Completion** — Final review, docs, persist learnings
-
-**🛑 MANDATORY STOPS** — After plan, after each batch, after completion.
-
-Refer to the Orchestrator agent's full instructions for the detailed workflow.

package/scaffold/claude-code/commands/aikit-plan.md

@@ -1,14 +0,0 @@
-# aikit plan
-
-> Create a detailed TDD implementation plan without executing it
-
-## Planning Workflow
-
-1. **AI Kit Recall** — Search for past plans, architecture decisions
-2. **FORGE Ground** — Classify tier, scope map, seed unknowns
-3. **Research** — Explore codebase, understand subsystems
-4. **Draft Plan** — 3-10 phases with agent assignments, TDD steps
-5. **Dependency Graph** — Group into parallel batches
-6. **Present** — Show plan with open questions
-
-**🛑 MANDATORY STOP** — Wait for user approval. Do NOT implement.

package/scaffold/claude-code/commands/aikit-review.md

@@ -1,23 +0,0 @@
-# aikit review
-
-> Dual-model code + architecture review pipeline
-
-## Review Pipeline
-
-### Step 1: Scope
-Identify changed files and their blast radius.
-
-### Step 2: Code Review (parallel)
-Launch Code-Reviewer-Alpha and Code-Reviewer-Beta on the same changeset.
-
-### Step 3: Architecture Review (if needed)
-If changes cross service boundaries or modify interfaces, launch Architect-Reviewer-Alpha and Architect-Reviewer-Beta.
-
-### Step 4: Synthesis
-Merge findings from both reviewers:
-- **Agreements**: Both found same issue → HIGH confidence
-- **Unique findings**: One found, other didn't → verify
-- **Disagreements**: Contradicting verdicts → present both to user
-
-### Step 5: Report
-Present unified review with: verdict, findings by severity, recommended actions.