initializer

Clarify objectives and split them into high-cohesion features via a subagent.

Updated Aug 23, 2026

Search Tags:#planning #specification #requirements #subagent #product-management #clarify #feature-boundary

Ready to run

npx skills add https://github.com/Serien3/SuperSpec --skill initializer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: initializer
Source: https://github.com/Serien3/SuperSpec/tree/main/src/superspec/skills/initializer
Command: npx skills add https://github.com/Serien3/SuperSpec --skill initializer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transforms ambiguous objectives into clear, cohesive feature boundaries by guiding a clarification step and optional subagent workflow.

Core Features & Use Cases

Clarifies objectives to reduce ambiguity and misalignment between stakeholders and engineers.
Splits objectives into the minimum number of high-cohesion features by identifying clear capability boundaries.
Coordinates a decision path (Simple-way vs Spawn-way) based on whether the objective is direct text or a referenced document.

Quick Start

Provide your objective text or reference documents and let the skill produce a refined feature-boundary proposal.

Frequently Asked Questions about initializer

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

FAQPage Schema

How do I clarify ambiguous product objectives before splitting them into features?▼

Clarifying ambiguous product objectives requires a structured specification process that reduces misalignment between stakeholders and engineers. This skill guides that clarification step to transform raw objectives into clear, cohesive feature boundaries before any development begins.

What is the best way to split a large feature request into high-cohesion requirements?▼

Splitting a large feature request into high-cohesion requirements is achieved by identifying clear capability boundaries. A feature-boundary subagent analyzes the objective and separates it into the minimum number of cohesive features needed.

How do I generate a feature specification from a referenced product document?▼

Generating a feature specification from a referenced document uses a spawn-way decision path. The skill reads the referenced document, clarifies the objective, and produces a refined feature-boundary proposal template for follow-on design work.

Can I use a subagent to define feature boundaries for direct text objectives?▼

Defining feature boundaries for direct text objectives uses a simple-way decision path without spawning a subagent. The skill processes the direct text input, clarifies the goal, and outputs a refined objective and proposal template directly.

Why does my product specification lack clear feature boundaries?▼

A product specification lacks clear feature boundaries when the initial objective contains unresolved ambiguity. Applying a dedicated clarification step identifies specific capability boundaries and splits the objective into the minimum number of high-cohesion features.

When should I not use automated feature boundary splitting for requirements planning?▼

Automated feature boundary splitting is not ideal when the initial objective lacks sufficient context for the subagent to identify capability boundaries. You should provide detailed direct text or a comprehensive referenced document to ensure accurate specification.