deep-plan-temporal

Use before touching code for any multi-step task via a durable Temporal-backed workflow that survives session crashes. Trigger phrases include "deep-plan temporal", "sagaflow plan", "durable plan", "temporal planning". Produces an ADR-backed plan with verification-backed acceptance criteria via a Planner → Architect → Critic consensus loop. Fire-and-forget — refine the plan while you do other work.

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 "deep-plan-temporal" with this command: npx skills add npow/skillsmp-npow-npow-deep-plan-temporal

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.

Related Skills

Related by shared tags or category signals.

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
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
Coding

team

Use when coordinating multiple agents on a staged pipeline — plan → PRD → exec → verify → fix — with independent critic/verifier gates and 4-reviewer parallel panel on every source modification. Trigger phrases include "spawn a team", "team of agents", "coordinate agents", "staged pipeline", "multi-agent pipeline", "agent team", "run a team on this", "PRD-driven team", "team workflow", "agents working together", "assemble a team", "delegate to a team", "orchestrate agents", "pipeline of agents". File-based state, no external MCP dependencies, honest termination labels, Claude Code native team tools.

Repository SourceNeeds Review
Research

deep-research-temporal

Use when researching, investigating, or exploring a topic systematically via a durable Temporal-backed workflow. Trigger phrases include "deep-research temporal", "sagaflow research", "durable research", "temporal research". Spawns parallel researchers across WHO/WHAT/HOW/WHERE/WHEN/WHY/LIMITS plus cross-cut dimensions (PRIOR-FAILURE, BASELINE, ADJACENT-EFFORTS, STRATEGIC-TIMING, ACTUAL-USAGE). Fact-verification, novelty classification, vocabulary bootstrap for cold-start topics. Fire-and-forget while you do other work.

Repository SourceNeeds Review
deep-plan-temporal | V50.AI