autopilot-runner

Automate complex workflows with a six-phase lifecycle and evidence enforcement.

2|Updated Jul 13, 2025

Search Tags:#workflow automation #software development #workflow validation #autopilot #Iron Rule

Ready to run

npx skills add https://github.com/krzemienski/shannon --skill autopilot-runner

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: autopilot-runner
Source: https://github.com/krzemienski/shannon/tree/main/skills/autopilot-runner
Command: npx skills add https://github.com/krzemienski/shannon --skill autopilot-runner

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the full lifecycle of a complex workflow, ensuring that tasks are executed autonomously and validated rigorously.

Core Features & Use Cases

Full-Lifecycle Automation: Manages the entire workflow from specification to execution, QA, validation, and cleanup.
Iron Rule Enforcement: Ensures all tasks are completed with evidence on disk and no verdicts are made without proof.
Multi-Perspective Validation: Validates tasks through functional, security, and quality/architecture perspectives.
Use Case: For a software development workflow, use this Skill to automatically plan, implement, and validate code changes without manual oversight.

Quick Start

To start the autopilot runner for a specific task, use the command: /shannon:autopilot --resume <run-id>

Frequently Asked Questions about autopilot-runner

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

FAQPage Schema

How do I automate complex software development workflows with built-in validation?▼

You can automate complex software development workflows using a six-phase lifecycle that includes multi-perspective validation, stall detection, and resume semantics. It manages the entire process from specification to QA and cleanup autonomously.

What is the Iron Rule in workflow automation and how does it enforce evidence?▼

The Iron Rule in workflow automation enforces transcript-evidence requirements, ensuring all tasks are completed with proof on disk and no verdicts are made without evidence. This guarantees rigorous validation for high-stakes production automation.

How do I resume an interrupted workflow automation task?▼

To resume an interrupted workflow automation task, use the resume semantics feature with a specific run identifier. This allows the automated lifecycle to pick up where it left off without losing prior execution progress.

Can I validate code changes automatically from security and architecture perspectives?▼

Yes, multi-perspective validation assesses code changes automatically through functional, security, and quality/architecture perspectives. This ensures comprehensive automated verification without manual oversight.

When do I need SDK harness instrumentation for workflow automation?▼

SDK harness instrumentation is needed for production-grade workflow automation requiring high stakes and evidence verification. It instruments the automated tasks to ensure rigorous execution and validation throughout the lifecycle.

Does this workflow automation approach handle stall detection in long-running processes?▼

Yes, this workflow automation approach includes stall detection to identify halted processes during complex lifecycle execution. It monitors tasks continuously to ensure autonomous workflows progress reliably without manual intervention.