spx-plan

Guide exploratory planning and codebase investigation for ambiguous requirements.

9|9|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/nullmastermind/viber-router --skill spx-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spx-plan
Source: https://github.com/nullmastermind/viber-router/tree/main/.claude/skills/spx-plan
Command: npx skills add https://github.com/nullmastermind/viber-router --skill spx-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams and individuals enter a disciplined "explore mode" to think through ambiguous requirements, investigate code, and clarify trade-offs before any implementation begins. It prevents premature coding by enforcing a stance of discovery, surfacing unknowns, and reducing verification failures later in the workflow.

Core Features & Use Cases

  • Exploratory Stance: Provides a Feynman-first thinking posture that restates requirements simply, surfaces gaps, and forces concrete choices.
  • Codebase Investigation: Guides targeted file reads, traces execution paths, and maps integration points without writing or modifying files.
  • Structured Decisioning: Always asks concrete A/B/C + Other options, offers recommendations grounded in repository patterns, and drafts verification steps.
  • Verification & Guardrails: Includes a Zero-Fog checklist and rules for when to run verification subagents; enforces "no implementation" and safe subagent usage.
  • Subagent Coordination: Prepares briefs for specialized subagents (research, docs, UI) and instructs them to report findings only.

Quick Start

Ask the assistant to "Help me explore and map the requirements for <feature> and identify the files and decision points I should investigate next."

Frequently Asked Questions about spx-plan

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

FAQPage Schema
How do I clarify ambiguous requirements before starting implementation?

Clarifying ambiguous requirements involves entering a discovery stance that restates needs simply, surfaces gaps, and forces concrete choices before coding. This approach uses guided questioning to map unknowns and establish clear trade-offs.

What is the best way to investigate codebase structure without writing code?

Investigating codebase structure without writing code requires targeted file reads, execution path tracing, and mapping integration points. This method safely explores the repository to identify decision points and patterns without modifying files.

How do I map decision trade-offs for a new feature?

Mapping decision trade-offs uses structured decisioning to present concrete A/B/C options and offer recommendations grounded in existing repository patterns. It drafts verification steps to validate choices against current architecture.

Can I coordinate research subagents during pre-implementation planning?

Coordinating research subagents during pre-implementation planning is possible by preparing briefs for specialized agents like research, docs, and UI. These subagents are instructed to report findings only, maintaining a strict no-implementation boundary.

When should I not use exploratory planning for my architecture?

Exploratory planning is not suitable when requirements are fully unambiguous and implementation can proceed immediately. It is designed strictly for discovery sessions and pre-implementation decision-making where unknowns and trade-offs exist.