Handles the whole task
Connects requirements to architecture, interfaces, data, state, security, reliability, migration, observability, rollout, testing, and alternatives.
Connects requirements to architecture, interfaces, data, state, security, reliability, migration, observability, rollout, testing, and alternatives. The Agent prepares a reviewable technical specification and keeps the evidence and open questions clear for review.
Provide code, schemas, requirements, or examples and explain the audience, decision, constraints, and definition of done.
Connects requirements to architecture, interfaces, data, state, security, reliability, migration, observability, rollout, testing, and alternatives.
Review a reviewable technical specification, resolve marked questions, and ask for changes in the same conversation.
Connects requirements to architecture, interfaces, data, state, security, reliability, migration, observability, rollout, testing, and alternatives.
Decisions, tradeoffs, assumptions, unknowns, operational risks, and acceptance criteria are explicit.
Continue in the same conversation to change the scope, emphasis, format, or level of detail in a reviewable technical specification.
Start with code, schemas, requirements, or examples. Add the audience, decision, constraints, preferred format, and anything that must remain unchanged.
Connects requirements to architecture, interfaces, data, state, security, reliability, migration, observability, rollout, testing, and alternatives.
Decisions, tradeoffs, assumptions, unknowns, operational risks, and acceptance criteria are explicit.
Yes. Keep working in the same conversation to revise a reviewable technical specification, answer open questions, or change the audience and format.
Keep working with the same material without moving it between separate products.
Use Vecbase for incident postmortem. Give the Agent your context, check the evidence, and refine a blameless, evidence-based incident postmortem.
Use Vecbase for architecture diagram. Give the Agent your context, check the evidence, and refine a readable architecture diagram with clear boundaries.
Use Vecbase for api documentation. Give the Agent your context, check the evidence, and refine accurate API documentation developers can use.
Vecbase
For Technical Specification, add code, schemas, requirements, or examples, explain what matters, and let the Vecbase Agent prepare a reviewable technical specification you can review and refine.