Use when a task must be driven to guaranteed completion through a PRD-driven persistence loop — breaking work into user stories with structured acceptance criteria, iterating story-by-story with independent verification, and terminating only when every criterion has fresh passing evidence and an independent reviewer approves. Trigger phrases include "keep going until done", "loop until complete", "don't stop until", "finish this completely", "iterate until done", "persistence loop", "PRD-driven execution", "work through all stories", "drive this to completion", "until all tests pass", "keep iterating", "loop this", "self-loop until finished". Honest termination labels; no self-approval.
This listing is imported from SkillsMP metadata and should be treated as untrusted until upstream source review is completed.
Install skill "loop-until-done" with this command: npx skills add npow/skillsmp-npow-npow-loop-until-done
This source entry does not include full markdown content beyond metadata.
This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.
Related by shared tags or category signals.
Critically reviews project proposals, grant applications, and business plans. Use when the user asks to review, critique, evaluate, or assess a proposal, pitch, grant application, or business plan for viability, competition, or flaws. Fact-checks claims, maps competitive landscape, identifies structural problems, and provides honest recommendations.
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.
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.
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.