sdlc-explore

Grounds raw ideas by dispatching parallel investigation, research, and recall workers into one explore.md.

Updated Sep 11, 2026
One-click install
npx skills add https://github.com/zhixuan312/zz-stack --skill sdlc-explore-zhixuan312
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdlc-explore
Source: https://github.com/zhixuan312/zz-stack/tree/main/catalog/sdlc/sdlc-flow/skills/sdlc-explore
Command: npx skills add https://github.com/zhixuan312/zz-stack --skill sdlc-explore-zhixuan312

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Raw ideas and brain dumps arrive ungrounded, and designing on them directly risks missing existing code, prior team decisions, or outside prior art. This Skill turns a raw idea into a structured exploration document before anyone commits to a design. ## Core Features & Use Cases - Parallel fan-out dispatch: Sizes and dispatches 3-12 subagent workers across three legs — internal investigation, external research, and prior-decision recall from the ZZ knowledge base — one question per worker. - Synthesis into explore.md: Writes a single initiative document with Background, Current state, and Rough direction sections, including 3-5 ranked candidate directions spanning at least two resolution shapes, each with citations or explicit sentinels. - Degraded-mode handling: Defines sentinel values and failure rules for each worker leg, including when not to write the artifact at all. - Use Case: A product manager brings a vague feature request about token expiry. The Skill captures the brain dump, dispatches investigations into the auth module and session layer plus a recall of prior decisions, then synthesizes ranked directions for the team to pick from before writing a spec. ## Quick Start Ask the agent to run sdlc-explore on your raw feature idea so it can fan out investigators and produce an explore.md with ranked directions.

Frequently Asked Questions about sdlc-explore

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

FAQPage Schema
How do I explore a raw feature idea before writing a spec?▼

Run sdlc-explore with the brain dump: it captures the idea, sizes a fan-out of investigation, research, and recall workers, dispatches them in parallel, then synthesizes one explore.md with Background, Current state, and 3-5 ranked directions.

What is the difference between sdlc-explore and sdlc-investigate?▼

sdlc-explore is divergent: it surveys many directions by dispatching multiple workers and synthesizing them. sdlc-investigate answers one convergent question with citations, and is itself dispatched as a worker inside the explore fan-out.

How many parallel workers does the exploration fan-out use?▼

The fan-out ranges from roughly 3 to 12 workers, sized by the number of distinct questions in the brain dump: 1-8 investigate workers, 0-3 research workers, and 1-3 recall workers. A typical feature lands around 5-1-1.

Can the recall leg of the knowledge base be skipped?▼

No, at least one sdlc-recall worker always runs because a superseded prior decision is the most valuable signal before design. An empty result is recorded as the sentinel (no prior learning), which is itself information.

What happens if exploration workers fail or return nothing?▼

Each failed leg maps to a sentinel: (no external source found), (no internal anchor — fully greenfield), or (no prior learning). If both investigate and research fail, or all three fail, the artifact is not written and every error is reported instead.

When should I not use sdlc-explore?▼

Do not use it for a single convergent question that needs one answer with citations — that is a single sdlc-investigate. It also requires a runtime that can dispatch subagents and reach the working tree directly.