Results for “deliverables”
10 skillsboost-prompt
Interactive prompt refinement workflow: interrogates scope, deliverables, constraints; copies final markdown to clipboard; never writes code. Requires the Joyride extension.
0
requirement-structuring
`analysis-agent`: use when raw requests need behavior, actors, scope, non-goals, constraints, deliverables, acceptance, or test traceability; skip when structure already exists.
4 · bundle
boost-prompt
Refines task prompts through iterative questioning about scope, deliverables, and constraints, then copies the final markdown to the clipboard.
36.2k
More results
delivery
Adaptive, resumable Git delivery across repositories and agent runtimes — probe policy, checkpoint coherent work, publish, review, integrate, and verify cleanup
8 · bundle
cloudflare-email-service
Send and receive transactional emails using Cloudflare Email Service, including Workers binding, REST API, Agents SDK integration, and email routing with deliverability setup.
2.1k · bundle
problem-to-plan
Tactical fast path: turn a small problem, bug report, edit request, or narrow refactor into three deliverables — a brief change-spec (docs/specs/), a detailed implementation-ready plan (docs/plans/), and a TODO.md with agent-pickable tasks and milestones. Load when the user describes a tactical problem and wants quick planning artifacts, says "plan this change", "create a TODO", "write a plan for this", "problem to plan", "break this into tasks for agents", "I want to change X — plan it", or when process-decomposer routes here after determining the user needs lightweight planning deliverables. Also triggers on "create tasks from this problem", "make this actionable", or "turn this into a plan agents can execute". For feature-sized work that needs an executable spec + constitution + cross-check gate, route to `spec-driven-development` (or `feature-spec`) instead.
3 · bundle
readability-guidance
Surfaces Han's shared Human-Readable Output Standard — the readability rule and the writing-voice profile — into the calling skill's own context, so the caller drafts in voice and runs its self-check against the current standard sourced from one canonical copy. Use when a prose-producing skill needs the shared readability standard available in context before it drafts. Governs the shape of a written deliverable, where explanation-guidance governs what a run says to a person in a turn. Runs in the caller's context and hands control straight back; it does not produce a deliverable of its own, rewrite anything, or judge the caller's work. Does not run the adversarial rewrite pass — dispatch the readability-editor agent for that, or use edit-for-readability to rewrite an existing target. Does not cover explaining technical work to a reader who will not implement it — use explanation-guidance for that.
218
digital-worked-example-sequence
Create an interactive digital worked example sequence with fading for online or blended delivery. Use when building e-learning modules, LMS content, or app-based instruction.
0
handoff-protocol
Use when passing work, tasks, or deliverables between agents. This skill provides a standardized protocol for agent-to-agent handoffs, ensuring context, requirements, and expectations are clearly communicated during task delegation or escalation.
0
output-validation-checklist
Use before delivering any work product to validate quality. This skill provides a standardized checklist that every agent must complete before marking work as done, ensuring consistent quality across all deliverables regardless of agent or company.
0