autopilot

Use when running full-lifecycle autonomous execution from a vague idea to working verified code — idea to battle-tested design to consensus plan to executed code to audited defects to three independent judge verdicts to honest completion report. Trigger phrases include "autopilot", "build me end to end", "full lifecycle", "idea to working code", "auto-run this project", "run this autonomously", "just build it", "go from idea to code", "do everything", "autonomous execution", "end-to-end build", "build this for me", "make it real end to end", "full autonomous build". Iron-law phase gates between every stage; no coordinator self-approval; honest termination labels.

Safety Notice

This listing is imported from SkillsMP metadata and should be treated as untrusted until upstream source review is completed.

Copy this and send it to your AI assistant to learn

Install skill "autopilot" with this command: npx skills add npow/skillsmp-npow-npow-autopilot

No markdown body

This source entry does not include full markdown content beyond metadata.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Open in GitHub

Related Skills

Related by shared tags or category signals.

Security

deep-qa

Use when reviewing, auditing, QAing, critiquing, or assessing any artifact — a spec, code change, diff, PR, research report, skill, prompt, or document — and you want parallel adversarial critic agents to find defects. Trigger phrases include "review this", "audit this", "QA this", "find issues", "find defects", "critique this", "check this for problems", "what's wrong with this", "evaluate this", "run QA", "review the diff", "review the PR", "review my code", "deep QA", "defect audit", "code review", "assess this". Produces a prioritized defect registry with severity-rated findings via parallel critic agents across artifact-type-aware QA dimensions. Does not fix defects — surfaces them for human triage.

Repository SourceNeeds Review

-3npow

Research

deep-debug

Use when a bug, test failure, or unexpected behavior needs diagnosing — including production incidents, regressions, stack traces, mysterious failures, flaky tests, or any symptom needing root-cause analysis. Trigger phrases include "debug this", "why is this failing", "find the bug", "fix the bug", "root cause", "what's wrong with", "this is broken", "diagnose", "troubleshoot", "investigate this failure", "the test is failing", "this used to work", "why doesn't this work", "where's the bug". Adversarial hypothesis-driven debugging with parallel competing hypotheses across orthogonal dimensions, blind independent judging, discriminating probes that falsify leaders, TDD-gated fix loops, and mandatory architectural escalation after 3 failed attempts.

Repository SourceNeeds Review

-3npow

Coding

deep-design

Use when designing, specifying, architecting, or drafting a design for any system, feature, product, protocol, game, or workflow, and you want adversarial stress-testing before writing code. Trigger phrases include "design this", "design the system", "architect this", "draft a design", "design a feature", "design spec", "stress-test the design", "battle-test the design", "find flaws in this design", "design review", "harden the design", "pressure-test the design", "think through the design". DFS-based flaw-finding with parallel critic agents that stress-test until coverage saturates. Output is a battle-tested design document with an honest coverage report.

Repository SourceNeeds Review

-3npow

Coding

deep-plan

Use before touching code for any multi-step task — features, refactors, migrations, architectural decisions, bug fixes, or any work that needs to be broken into verifiable steps. Trigger phrases include "write a plan", "implementation plan", "plan this", "plan the work", "break this down", "how should I approach this", "make a plan", "design the approach", "before I code this", "I need a plan", "write up the plan", "spec to plan", "requirements to plan". Produces an ADR-backed plan with verification-backed acceptance criteria via a Planner → Architect → Critic consensus loop.

Repository SourceNeeds Review

-3npow