deliver-work

Route vague software requests into structured plan-and-execute delivery workflows.

Updated Sep 25, 2024
One-click install
npx skills add https://github.com/kwam1na/athena --skill deliver-work
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deliver-work
Source: https://github.com/kwam1na/athena/tree/main/.agents/skills/deliver-work
Command: npx skills add https://github.com/kwam1na/athena --skill deliver-work

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts user requests for software work into a structured, end-to-end delivery flow by routing through a default compound kernel when no more specific skill is applicable.

Core Features & Use Cases

  • Default entrypoint for software delivery that translates vague requests into a plan-and-execute workflow, including planning, test-first or characterization-first approaches, repository sensors for validation, review, and handoff.
  • Route-specific guidance and guardrails: apply the compound-delivery-kernel, decide when to create tickets, brainstorm when requirements are fuzzy, and use appropriate sub-skills for debugging or code review.
  • Handoff and learning: capture outcomes, tests, and learnings for durable improvements and future automation.

Quick Start

Invoke compound delivery to plan, execute, validate, review, and hand off software work end-to-end.

Frequently Asked Questions about deliver-work

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I coordinate end-to-end software delivery from a vague work request?▼

To coordinate software delivery, vague work requests are routed through a default compound kernel that structures an end-to-end plan. This plan-and-execute workflow covers planning, testing, validation, review, and handoff.

What is a compound delivery kernel for software workflow?▼

A compound delivery kernel is a default routing mechanism that translates vague software work into structured end-to-end delivery flows. It applies guardrails to decide when to create tickets, brainstorm fuzzy requirements, and guide validation.

How do I plan and validate software work using repository sensors?▼

Software work validation uses repository sensors to verify test-first or characterization-first approaches during execution. The compound delivery framework applies these sensors to ensure code meets requirements before review and handoff.

When should I brainstorm requirements during software delivery planning?▼

Brainstorming requirements is triggered when software work requests are fuzzy or lack clear specifications. The compound delivery kernel applies guardrails to route these ambiguous tasks to a brainstorming phase before creating a structured plan.

How does software delivery handoff capture learnings for future work?▼

Software delivery handoff captures outcomes, tests, and learnings to drive durable improvements and future automation. This learning loop ensures the compound delivery framework continuously refines its end-to-end orchestration and routing behavior.