decompose

Interview project scope and generate a manifest of sub-features with dependencies.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/tercel/spec-forge-gemini --skill decompose-tercel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: decompose
Source: https://github.com/tercel/spec-forge-gemini/tree/main/skills/decompose
Command: npx skills add https://github.com/tercel/spec-forge-gemini --skill decompose-tercel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Lightweight project decomposition helps teams decide whether to treat a project as a single feature or split into multiple sub-features, then generate a manifest when needed.

Core Features & Use Cases

  • Lightweight 3-5 round interview to capture scope boundaries
  • Generates a project manifest listing sub-features, dependencies, and execution order (for multi-split projects)
  • Keeps effort focused on boundaries and dependencies without demand validation or deep research

Quick Start

Invoke the decompose workflow on your project to decide between a single feature and a multi-split, then generate a project manifest of sub-features if needed.

Frequently Asked Questions about decompose

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

FAQPage Schema
How do I break down a project scope into sub-features?

A project manifest lists sub-features, dependencies, and execution order. It is generated after a lightweight 3-5 round interview determines that splitting the project scope into sub-features is appropriate.

When should I split a project into sub-features instead of treating it as a single feature?

This decomposition process focuses strictly on boundaries and dependencies. It avoids demand validation and deep research beyond scope boundaries to keep effort lightweight within the spec-forge chain context.

What is included in a project manifest for sub-features?

No, this decomposition process avoids demand validation and deep research beyond scope boundaries. It focuses exclusively on capturing scope boundaries and generating a manifest of sub-features within the spec-forge chain context.

Does project decomposition require deep research into scope boundaries?

Before decomposing, you need a defined project scope to analyze. The skill operates within the spec-forge chain context, so having your project boundaries and goals ready for a 3-5 round interview is the primary prerequisite.

Can I generate a project manifest without splitting the project into multiple sub-features?

Yes, the project manifest explicitly lists dependencies and execution order for the sub-features. This ensures that after splitting the scope, you have a clear sequence and understanding of how the sub-features interact.