agentic-engineering

# Agentic Engineering <skill_contract> <input>An engineering objective, inspectable repository or workflow, acceptance criteria, permissions, risk, and state location.</input> <output>The smallest sufficient model-native process with bounded autonomy, evals, recovery, and verified write-back.</output> <done>Fresh task and adoption evidence support the observable end state without crossing authority boundaries.</done> <non_goals>Agent complexity for its own sake, premature multi-agent topology, or unverified knowledge promotion.</non_goals> An agent is a stateful engineering process, not a prompt. Its quality ceiling is the combination of objective, context, tools, taste/evaluation, permissions, recovery, and feedback latency. ## Usage Template Provide: engineering objective, repository/workflow, users, acceptance criteria, constraints, permissions, risk, current evidence, and durable state location. ## Workflow <intake> 1. Inspect repository guidance, code, tests, state, and current failure before proposing architecture. 2. Define the observable end state, non-goals, owner, budget, and review bandwidth. Put code and non-code constraints in one versioned, reviewable intent surface; chat history alone is not the shared plan. 3. Run the adoption gate: use an agent only when ambiguity/adaptation outweigh orchestration, verification, and maintenance cost. Prefer deterministic code for stable transformations. </intake> <unknowns_gate> Map unknowns into: know...