Add missing commands & agents

[jabrena]

Summary

Complete command and agent coverage across the development lifecycle.

The analysis and design priority has been implemented through #806 and merged in #807. The remaining gap is operation workflow design and implementation.

Implementation status

Analysis and design: implemented

Implemented by #806 and merged in #807 on June 7, 2026.

Command	Agent ownership	Backing skills or capability	Status
/create-issue	@robot-business-analyst	043-planning-github-issues, 044-planning-jira	✅ Implemented
/create-feature-branch	Git workflow utility	Extended for repository-backed analysis/design artifacts	✅ Implemented
/create-worktree	Git isolation utility	Isolated branch and linked worktree creation	✅ Implemented
/explore-design	@robot-architect	034-architecture-design-exploration	✅ Implemented
/create-adr	@robot-architect	030, 031, and 032 architecture ADR skills	✅ Implemented
/create-diagram	@robot-architect	033-architecture-diagrams	✅ Implemented
/create-plan	@robot-tech-lead	Refactored 041-planning-plan-mode	✅ Implemented
/create-spec	@robot-tech-lead	Refactored 042-planning-openspec	✅ Implemented
/review-alignment	@robot-business-analyst	Read-only traceability and readiness review	✅ Implemented

The original proposal for a separate @robot-planner was superseded. The existing @robot-coordinator was renamed to @robot-tech-lead and extended with three missions:

• Create implementation plans.
• Create OpenSpec changes independently from plans.
• Coordinate delivery through the existing framework-specific coder agents.

Additional delivered work:

• Added @robot-architect to the canonical generated agent bundle.
• Extended @robot-business-analyst with issue creation and read-only alignment review.
• Added independent issue-to-plan, issue-to-spec, plan-to-spec, and spec-to-plan paths.
• Defined artifact authority and prevented silent two-way synchronization.
• Updated command and agent installers, inventories, tests, READMEs, and localized guides.
• Completed and archived the related OpenSpec parent and four child changes.
• Passed XML, Maven (823 tests), Markdown, generated-skill, security scanner, SkillSpector, pre-commit, and OpenSpec validation.

References:

• Analysis/design story: Add analysis and design workflow commands and agents #806
• Merged implementation: feat(workflows): add analysis and design lifecycle #807

Development: implementation alignment pending

The existing implementation commands and coder agents remain available:

• /implement
• @robot-java-coder
• @robot-spring-boot-coder
• @robot-quarkus-coder
• @robot-micronaut-coder

The coder agents already exist, but the generic /implement command still needs to be aligned with @robot-tech-lead, selected plan/OpenSpec authority, framework routing, parallel groups, task status, and verification evidence. This work is tracked by #809.

Operation: pending

Operation coverage still needs a focused design decision before implementation:

Candidate capability	Potential command	Potential owner	Relevant skills	Status
Runtime profiling	/profile	@robot-profiler	161-164 profiling skills	⏳ Pending design
Performance testing / benchmarking	/benchmark	@robot-profiler	151-152 and existing JMH guidance	⏳ Pending design

The operation command names, boundaries, inputs, outputs, and agent ownership must be agreed before implementation.

Remaining deliverables

• Define operation workflow boundaries and ownership.
• Decide whether profiling and benchmarking require separate agents.
• Create OpenSpec change(s) for the approved operation scope.
• Implement the selected operation commands and agents.
• Update inventories, installation assets, lifecycle documentation, and validation coverage.

Acceptance criteria

Analysis and design

• Each analysis/design command has a clear purpose, documented inputs, workflow, backing capabilities, safeguards, and output.
• Planning is owned by @robot-tech-lead through 041-planning-plan-mode.
• OpenSpec creation is owned by @robot-tech-lead through 042-planning-openspec.
• @robot-architect distinguishes design exploration, ADR creation, and diagram generation.
• Command and agent source assets are maintained under skills-generator/src/main/resources/.
• Command and agent inventories and installation guidance are synchronized.
• Relevant XML, Maven generator, Markdown, generated-skill, scanner, and OpenSpec validations pass.

Operation

• Operation command names and agent responsibilities are documented without overlapping ownership.
• The approved operation scope is captured in OpenSpec before implementation.
• Selected operation commands and agents are implemented.
• Operation inventories, installation guidance, documentation, and validation remain synchronized.

Out of scope

• Adding more implementation-phase commands or coding agents without a separately identified gap.
• Implementing operation commands before their scope and ownership are agreed.

[jabrena]

Implementation child created: #808

This child covers the implementation-ready /profile and /benchmark workflows with a new @robot-performance-engineer, backed by skills 151, 152, and 161-164. Deployment remains a separate follow-up because its platforms, safeguards, and backing skills are not yet agreed.

[jabrena]

Development child created: #809

This child aligns the existing /implement command with @robot-tech-lead, approved plan/OpenSpec execution artifacts, framework-specific coder delegation, dependency and parallel-group handling, OpenSpec task status, and verification gates. It intentionally reuses the existing coder agents rather than adding another development role.