v1.2.0

Overview

This release adds a safe, high-throughput parallel workflow for autonomous agents, plus installer improvements that make upgrades predictable and CI-friendly.

Why this matters for autonomous development

Parallel execution is only valuable if it doesn't introduce conflict, hidden coupling, or unsafe merges. The new ticket-based workflow formalizes ownership, blockers, and review gates so multiple agents can work simultaneously without stepping on each other. It also preserves the orchestrator's full-project context for integration decisions, while letting subagents operate in clean, isolated worktrees.

What's new

Ticket Builder parallel workflow

• New ticket-builder agent + skill to execute exactly one implementation-plan task in an isolated worktree.
• Required plan metadata (Parallel, Blocked by, Owned files) so tasks can be parallelized safely.
• Strict safety gate: subagent cannot commit/merge/push; orchestrator must review diffs before integration.
• Owned files validation script to detect overlapping file ownership before parallelizing.
• Workflow docs and templates updated with examples and clear handoffs.

Installer reliability improvements

• Skill/agent update prompts now support all/none/individual choices for safer upgrades.
• Non-interactive detection skips prompts in CI or headless runs to avoid hangs.
• Automatic backups for updated skills/agents to preserve user customization.

How this improves quality

• Reduces merge conflicts by enforcing explicit file ownership and blocker awareness.
• Prevents silent regressions through mandatory review gates on every parallel ticket.
• Scales throughput while keeping a single orchestrator responsible for integration decisions.
• Improves upgrade safety by making installer changes explicit and reversible.

References

• agents/ticket-builder.md, skills/ticket-builder/SKILL.md
• skills/writing-plans/SKILL.md (Parallel/Blocked by/Owned files guidance)
• docs/WORKFLOW_REFERENCE.md and docs/GETTING_STARTED.md
• install.sh