agentic-delivery-skills

Preserves useful state across long agent sessions, context compaction, handoffs, and restarts. Use when compressing context, handing work between agents, resuming after interruption, writing session summaries, or preventing repeated work.

Enforces a design/spec approval gate before production implementation. Use when UI, UX, product flows, architecture, API shape, prototypes, visual direction, or user-facing behaviour need signoff before builders write production code.

Keeps agent work safe in messy repositories. Use when git status is dirty, unrelated files exist, generated artefacts are present, multiple agents share a repo, or you must commit only the intended slice without damaging someone else's work.

Proves model and provider capability claims before changing agent defaults. Use when swapping models, checking context windows, reasoning effort, tool use, streaming, media support, OAuth entitlement, fallback behaviour, or provider-specific runtime paths.

Converts bug reports, screenshots, user panic, QA notes, and vague complaints into durable engineering briefs. Use when turning observed failures into reproducible issues with severity, expected behaviour, evidence, scope, owner, and acceptance tests.

Defines strict review-then-fix authority for reviewers. Use when a reviewer is allowed to repair findings after review, when avoiding reviewer-as-stealth-builder drift, or when verifying that fixes stay limited to documented findings.

Defines safe sandbox-to-production promotion gates for agent-built software. Use when deploying, restarting, promoting builds, validating runtime surfaces, checking rollback readiness, or proving that the running production artefact matches the reviewed source commit.

Performs security intake before importing external code, scripts, MCP servers, skills, packages, or GitHub repos. Use when copying, installing, operationalising, or running third-party artefacts in an agent harness or developer environment.

Makes agent and subagent work visible, inspectable, and task-local. Use when hidden background workers, child agents, tool calls, run IDs, task rails, progress streams, or parent-thread summaries must prove what is happening without leaking unrelated work.

Disciplined agentic engineering workflow for clarifying scope, writing build plans, breaking work into vertical slices, designing uncertain interfaces, using TDD tracer bullets, converting QA into durable briefs, and deepening architecture. Use when work needs a plan, refactor path, issue breakdown, test-first implementation, or handoff between agents.

Use when reviewing code adversarially or building production-bound features where rigour matters more than speed. Required for code reviews ending in a verdict (PASS/HOLD), when verifying that "tests pass" actually proves a feature works end-to-end, before closing findings as non-issues, before signing off your own work for peer audit, or when an author has already self-reviewed and you need to confirm or push back.

Formalises orchestrator, builder, reviewer, reviewer-fix, and final signoff workflows across agent harnesses, coding agents, and subagents. Use when coordinating multi-agent delivery, writing briefs, assigning builders or reviewers, deciding whether reviewers may fix issues, or final-signing production-bound work.