deliver

Convert rough engineering ideas into structured Markdown execution plans.

2|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/nodatall/primedirective --skill deliver-nodatall
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deliver
Source: https://github.com/nodatall/primedirective/tree/main/skills/deliver
Command: npx skills add https://github.com/nodatall/primedirective --skill deliver-nodatall

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates the chaos of ad-hoc, unplanned coding work that leads to missed requirements, rework, and unclear progress by providing a structured, repeatable workflow for turning rough ideas into approved, executable plans with built-in validation and review steps.

Core Features & Use Cases

  • End-to-end execution workflow: Turns rough ideas into readable Markdown execution plans, with optional deep research and Pro analysis passes to validate assumptions before implementation.
  • Built-in guardrails: Enforces plan refinement loops, user review checkpoints, and stop conditions to avoid unsafe, incomplete, or off-scope implementation.
  • Composable with other skills: Integrates with plan review, goal planning, and shared reference workflows for specialized use cases like adversarial plan review or long-running goal tracking.
  • Use case example: If you have a rough feature idea for your codebase, use this skill to generate a structured, reviewable execution plan, run optional research to validate current best practices, then implement it step-by-step with automatic validation and archiving.

Quick Start

Use the deliver skill to turn your rough feature or bug fix idea into a structured, reviewable execution plan, run optional deep research and Pro analysis passes, refine the plan, and implement it after your approval.

Frequently Asked Questions about deliver

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

FAQPage Schema
How do I turn a rough feature idea into a structured execution plan?

An execution plan workflow converts rough engineering ideas into structured, reviewable Markdown documents, applying optional deep research and Pro analysis to validate assumptions before step-by-step implementation begins.

How does an agile execution workflow handle code review and implementation validation?

An agile execution workflow handles code review by enforcing plan refinement loops, user review checkpoints, and stop conditions during step-by-step implementation, ensuring automatic validation and archive management before final commit finalization.

Can I use this implementation workflow for both bug fixes and architecture changes?

Yes, this structured implementation workflow applies to feature development, bug fixes, and architecture changes by generating reviewable execution plans with validation steps to prevent unsafe or off-scope implementation.

What is the best way to prevent ad-hoc implementation errors in software engineering?

The best way to prevent ad-hoc implementation errors is to adopt a structured workflow that transforms rough ideas into reviewable execution plans with refinement loops, user review checkpoints, and stop conditions to avoid off-scope implementation.

Do I need deep research to generate a code execution plan?

No, deep research is an optional integration used to validate assumptions and current best practices during plan refinement, allowing you to proceed with step-by-step implementation after user approval even without it.

When should I not use a structured workflow for code delivery?

You should avoid using a structured code delivery workflow when your task requires rapid, unstructured prototyping without review checkpoints, as the process enforces plan refinement loops, user approval, and stop conditions that intentionally slow down ad-hoc execution.