CaduAzeredo
- 9 skills
- 0 followers
- 15 hours ago last updated
- ▌
- ▌
- ▌
- ▌ Handoff · caduazeredoProduces an auditable, self-contained closing document for a session or round, addressed to another agent or a human. It records context and rationale, delivered versus pending scope, execution order in blocks separated by mandatory human checkpoints, numbered verifiable validation criteria including blocking gates, and an explicit blocked and out-of-scope list. Use when ending a work session, transferring execution to another agent, or pausing a round at a human checkpoint.
- ▌ To Spec · caduazeredoConverts validated context and domain understanding into an executable specification with scope, non-scope, expected behavior backed by verifiable acceptance criteria, error cases, dependencies, and risks — one spec per deliverable unit. Use when a deliverable is ready to be specified for implementation, or when an implementation deviated from its spec and the spec must be revised before work continues.
- ▌ Implement · caduazeredoImplements code against an approved spec in the project repository, adversarially re-verifying every finding at file:line before touching it (Confirmed, Partial or Refuted — refuted findings never become edits), one feature at a time and closed before the next (implemented, tested, whole suite green), with testability treated as a design constraint rather than a final step, small diffs, tests accompanying the code, Conventional Commits, and a ticket kept as an execution diary where every decision and deviation is recorded and justified. Use when a current spec exists and the operator has explicitly authorized writing to the project repository; when feasibility is still the open question, a throwaway prototype comes first, and scope deviations route back to to-spec instead of being improvised.
- ▌
- ▌ Domain Modeling · caduazeredoExtracts entities, relationships, invariants, and lifecycle states from a validated CONTEXT.md, naming everything with the business vocabulary and recording both the modeling decisions and what is deliberately left out. Use when a project has a current CONTEXT.md but no DOMAIN.md, when the existing domain model is outdated, or before writing specs that depend on domain rules.
- ▌ Grill With Docs · caduazeredoInterrogates real documentation and code before any planning. It collects primary sources, formulates the questions the material must answer, records gaps and contradictions explicitly instead of filling them with assumptions, and interviews the operator about what the sources leave open. Use when starting work on a project or feature that has no current CONTEXT.md, when onboarding an agent to an unfamiliar repository, or when the existing context is stale or contradicts the code.