Results for “phases”

14 skills
More results
jorcan
demo
Narrates a demo video for Loki Mode, a multi-agent autonomous startup system for Claude Code, covering setup, phases, and features.
0 · bundle
tools-only
ost
Runs an Opportunity Solution Tree workflow with a lightweight graph database and CLI, routing through outcome, opportunity, solution, and assumption phases.
7 · bundle
huuanh20
ck-plan-json
Creates a machine-readable phased JSON plan bundle from a spec or feature description, producing a compact master manifest plus per-phase step files for resumable execution.
1 · bundle
georgeqle
plan-phase
Decompose a single roadmap phase into implementation steps, tests, and file-level detail
1 · bundle
alirezarezvani
board-meeting
Runs a structured 6-phase multi-agent board meeting protocol for strategic decisions, with isolated C-suite contributions, critic analysis, synthesis, founder review, and decision extraction.
20.4k · bundle
a5c-ai
roadmap-management
Roadmap parsing, analysis, and mutation operations for ROADMAP.md. Handles phase and milestone lifecycle including add, insert (decimal), remove, complete, and requirements coverage analysis.
1.7k · bundle
kursku
gsd-add-phase
Add phase to end of current milestone in roadmap
55
subvisual
feature
Use when driving a feature prompt to a production-ready PR through discovery, definition, design, spec, issues, and dev phases, or when the user runs /feature or /feature resume — orchestrates the A-Team agentic pipeline over a target repo.
0 · bundle
testdouble
stakeholder-summary
Produces a plain-language stakeholder summary from an existing feature specification, for sharing with non-technical stakeholders before implementation kicks off. Use when the user wants to draft a stakeholder summary, executive summary, or business summary of a feature spec or PRD. Does not write the spec itself — use plan-a-feature. Does not sequence the build into phases — use plan-a-phased-build. Does not produce an implementation plan — use plan-implementation.
218 · bundle
dvy1987
adversarial-hat
Put on the adversarial hat and systematically attack any document, plan, strategy, or idea to expose its weakest points before commitment. Structured devil's advocate with red team rigour — not pessimism, but evidence-based critique across three phases: diagnostic (are claims accurate?), creative (is the problem artificially constrained?), challenge (are solutions robust?). Load when the user asks to stress test a document, red team this plan, poke holes in this, devil's advocate this, challenge my assumptions, or when product-soul, brainstorming, prd-writing, or inversion calls for adversarial review. Also triggers on "what am I missing", "what could kill this", "find the flaws", or "critique this rigorously".
3 · bundle