Agentic Development
Use AI agents in enterprise development with context packs, scoped tasks, and review gates.
Agentic development works when agents receive the right context, operate inside clear ownership boundaries, and produce changes that humans can review. It fails when agents are treated as unlimited autonomous developers without system knowledge.
Agent Workflow
Context Pack
| Section | Contents |
|---|---|
| Goal | User problem, acceptance criteria, non-goals |
| System map | Relevant apps, packages, APIs, ownership |
| Constraints | Style, security, performance, compatibility |
| Commands | Typecheck, tests, build, local server |
| Risks | Known edge cases and review focus |
Task Scoping
- Assign agents to concrete, bounded work.
- Keep write ownership clear when multiple agents work in parallel.
- Ask for changed file paths and verification results.
- Review generated code with the same standards as human code.
- Save recurring workflows as skills or templates only after they prove useful.
Governance
Agent outputs must pass normal CI and code review. High-risk changes involving auth, payments, secrets, legal copy, or deployment configuration require explicit human approval.