# Plan Requirements with Interactive Questions

Ambiguous project requests often lead to missing requirements and rework. This skill guides Claude, Codex, and Claude Code through structured question batches.

## Install

```bash
npx skillstore add dnyoussef/interactive-planner
```

## Metadata

- Status: approved
- Slug: dnyoussef-interactive-planner
- Version: 1.0.0
- Author version: 1.0.0
- Skillstore revision: r1
- Version status: valid
- Tree hash: 148b7fa58391eb5338f4e325e1a135e0b6e647914436b3d2651a36ee2e669689
- Author: DNYoussef
- GitHub username: DNYoussef
- License: MIT
- Repository: https://github.com/DNYoussef/ai-chrome-extension/tree/main/.claude/skills/interactive-planner
- Ref: 72d5025b022c77f7a51bdf5c1637c689c80e89d1
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 80
- Quality tier: silver
- Public page: https://skillstore.pages.dev/skills/dnyoussef-interactive-planner
- Manifest: https://skillstore.pages.dev/api/skills/dnyoussef-interactive-planner/manifest

## Capabilities

- Designs four-question batches for project scoping.
- Guides multi-select choices for non-exclusive decisions.
- Covers scope, architecture, user experience, quality, and constraints.
- Synthesizes answers into an actionable project specification.
- Defines input and output contracts for planning sessions.
- Includes example question sets for localization and OAuth work.

## Use Cases

- Scope a New Product Feature: Collect feature goals, user needs, constraints, and success criteria before development starts.
- Clarify Technical Architecture: Ask structured questions about frameworks, storage, authentication, testing, and deployment choices.
- Prepare Client Project Briefs: Turn a broad client request into a clear specification with assumptions and open questions.

## Prompt Templates

### Start Basic Planning

```
Use interactive-planner to scope my project. Ask one batch of questions about the goal, users, timeline, and must-have features.
```

### Plan a Feature Addition

```
Use interactive-planner for a new feature. Ask about user roles, core workflow, data needs, integration points, and testing expectations.
```

### Gather Architecture Requirements

```
Use interactive-planner with multiple batches. Cover framework, backend, storage, authentication, deployment, observability, scalability, and security constraints.
```

### Create a Complete Project Specification

```
Use deep interactive planning. Ask enough structured questions to produce a complete specification, list assumptions, and identify unresolved decisions.
```

## Limitations

- It does not implement code or run tests.
- It requires user responses to complete planning.
- It works best when an interactive question tool is available.
- It can be excessive for simple tasks with clear requirements.

## Best Practices

- Start with broad scoping questions before detailed architecture choices.
- Use multi-select only when options can be combined.
- Summarize answers and confirm unresolved decisions before implementation.

## Anti Patterns

- Do not use it when the user already provided a complete specification.
- Do not ask overlapping questions that force unclear choices.
- Do not continue asking batches when a small direct task is clear.

## Security Audit

- Audited at: 2026-07-06T12:31:51.791\+00:00
- Summary: All static findings were adjudicated as false positives. The flagged backticks are Markdown or YAML fences, and the network reconnaissance alerts are metric names in documentation.

## Stats

- Views: 159
- Downloads: 8
- Favorites: 2
- Popularity score: 0