The mandate
Produce an implementation plan that respects the repository already in front of you.
Plans architecture, repository structure, delivery slices, infrastructure, tests, and deployment readiness.
The Tech Agent records architecture, ownership, data flows, alternatives, tests, observability, migrations, deployment, and rollback. It favors vertical slices and existing conventions over architecture designed in isolation.
What to bring
Bring the repository, current boundaries, constraints, and one verifiable milestone.
The agent needs enough technical context to distinguish a genuine constraint from a preference and a required migration from speculative infrastructure.
- 01
The product, repository, service, or technical boundary being planned.
- 02
Languages, frameworks, data stores, infrastructure, and repository conventions.
- 03
Current boundaries, data flows, ownership, known debt, and relevant decision records.
- 04
Delivery, reliability, security, migration, budget, compatibility, and operational constraints.
- 05
The independently verifiable technical outcome and target release.
What you receive
Architecture decisions tied directly to a test-first delivery path.
Decision records, delivery slices, and the release runbook stay connected so implementation, verification, deployment, and rollback tell one story.
- 01
Architecture and decision records
tech/architecture.mdReady when
Boundaries, data ownership, tradeoffs, and rejected options are recorded.
- 02
Test-first delivery plan
tech/delivery-plan.jsonReady when
Slices, dependencies, tests, owners, and acceptance criteria are explicit.
- 03
Release and rollback runbook
tech/release-runbook.mdReady when
A build can be observed, verified, deployed, and safely reversed.
The method
Inspect first, decide visibly, and deliver in reversible slices.
The plan is grounded in the source-backed workspace and turns every material host effect into an explicit request.
- 1
Inspect
Read repository conventions, boundaries, data ownership, deployment behavior, and known constraints.
- 2
Decide
Record alternatives, tradeoffs, ownership, interfaces, and rejected options.
- 3
Slice
Create test-first vertical deliveries with migrations, observability, and acceptance evidence.
- 4
Release
Define build, secret, deployment, verification, recovery, and rollback requests with approvals.
Signals & guardrails
An elegant architecture is a failure if it outruns the validated product.
Hidden scripts, unowned data, missing rollback evidence, broad secret access, or deployment before security review stop the delivery plan.
Signs the work is useful
- Lead time to verified release
- Change failure rate
- Primary workflow reliability
Reasons to pause
- Architecture exceeds validated product needs
- Deployment proceeds without security and rollback gates
Approval boundary
Repository mutation · Deployment · Secret access
Technical appendix
The exact contract behind the profile.
Useful for operators who need to inspect the immutable Kit version, typed boundary, and verification surface.
- Kit
- company-suite@0.1.0
- Entrypoint
- plan-tech
- Function
- plan-tech
- Runtime
- python@3.12
- Input
- specialist-brief.schema.json
- Output
- specialist-plan.schema.json
Verification
specialist-plan-quality · tech-readiness
Connected systems
Adios Git · Adios Workspace · Adios Deployments · Adios Secrets