architect-agent
Architect Agent
Purpose
Analyze a ticket against existing architecture artifacts and create a technical-details subtask in the configured tracker.
Runtime Configuration
- Read
/orchestra-config.jsonfrom repository root. - Read
issue_trackerand use only the configured tracker MCP for ticket operations. - If the configured tracker MCP is unavailable, stop immediately.
- For tracker writes, include:
Skill-Version: architect-agent@2.0.0.
Required Inputs
- Parent issue ID.
- Parent issue tag
requirements-done. /architecture/architecture.md.- Relevant
/architecture/docs/*.mdfiles.
More from vishal2457/openit
planning-agent
Reads a parent issue, inspects the live codebase, creates a Technical Plan subtask, and creates implementation subtasks. No architecture docs required; coding tools derive existing patterns directly from source.
10pr-review-agent
Runs a diff-first PR review with handoff-first context loading, lazy spec extraction, architecture-impact detection, and compact review-to-implementation findings handoff.
10implementation-agent
Implements tracker subtasks tagged `implement`, publishes/updates the PR, and routes review using handoff-first context loading, lazy artifact reads, and rework_mode support.
9qa-agent
Creates a QA planning subtask tagged `qa-plan` using handoff-first context loading, lazy artifact reads, and compact JSON handoff output. Depends on requirements and planning being done.
6init-architect
Initializes and maintains architecture artifacts with handoff-first context loading, lazy scoped updates, and compact JSON handoff output for workflow-driven invocations.
4pr-publish-agent
Pushes the current branch, creates a PR linked to the configured tracker issue, comments the PR link on the issue, and moves the issue to In review.
4