iloom: a developer workflow system delivered as a CLI and a VS Code extension for structured AI-assisted development. The CLI is the system of record, running tasks in isolated workflows and persisting analysis, plans, and decisions to your issue tracker, while the VS Code extension exposes insights, assumptions, risks, and decisions in real time.
Agent
This directory contains phase agent definitions as Markdown files with YAML frontmatter. They are loaded by AgentManager, rendered to .claude/agents/ in worktrees, and invoked as skills during workflows.
Agent
Use this agent to review workflow artifacts (enhancements, analyses, plans, implementations) before posting. The agent validates quality and completeness against artifact-specific criteria and provides actionable feedback for improvements.\n\nExamples:\n \nContext: Orchestrator wants to review an enhancement before…
Agent
Use this agent to review code changes.
Agent
Use this agent to detect a project's language and framework, then generate appropriate build/test/dev scripts for non-Node.js projects. The agent creates .iloom/package.iloom.json with shell commands tailored to the detected stack. Use this for Python, Rust, Ruby, Go, and other non-Node.js projects that don't have a…
Agent
Combined analysis and planning agent for SIMPLE tasks. This agent performs lightweight analysis and creates an implementation plan in one streamlined phase. Only invoked for tasks pre-classified as SIMPLE (< 5 files, <200 LOC, no breaking changes, no DB migrations). Use this agent when you have a simple issue that…
Agent
Use this agent when you need to analyze and research issues, bugs, or enhancement requests. The agent will investigate the codebase, recent commits, and third-party dependencies to identify root causes WITHOUT proposing solutions. Ideal for initial issue triage, regression analysis, and documenting technical findings…
Agent
Use this agent when you need to quickly assess the complexity of an issue before deciding on the appropriate workflow. This agent performs a lightweight scan to classify issues as SIMPLE or COMPLEX based on estimated scope, risk, and impact. Runs first before any detailed analysis or planning.
Agent
Use this agent when you need to analyze bug or enhancement reports from a Product Manager perspective. The agent accepts either an issue identifier or direct text description and creates structured specifications that enhance the original user report for development teams without performing code analysis or suggesting…
Agent
Use this agent when you need to implement an issue exactly as specified in its comments and description. This agent reads issue details, follows implementation plans precisely, and ensures all code passes tests, typechecking, and linting before completion. Examples:\n\n \nContext: User wants to implement a specific…
Agent
Use this agent after an implementation phase completes to independently verify that the phase's must-haves/invariants from the plan are actually met in the worktree. The agent gathers its own evidence (reads files, runs targeted tests) and returns a GO/NO-GO verdict per must-have. It reports violations but never fixes…
Agent
Use this agent when you need to analyze issues and create detailed implementation plans. This agent specializes in reading issue context, understanding requirements, and creating focused implementation plans with specific file changes and line numbers. The agent will document the plan as a comment on the issue without…
Agent
Wave verification agent that checks must-have criteria from child issues after each swarm wave, invokes fix skills for failures, and reports structured results.\n\nExamples:\n \nContext: Orchestrator wants to verify that wave 1 work meets acceptance criteria\nuser: "Verify must-haves for issues #101, #102, #103 from…