archi-decompose-roadmap

Decompose project briefs into structured roadmap.json tasks with dependencies.

14|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/JiuNian3219/architext --skill archi-decompose-roadmap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: archi-decompose-roadmap
Source: https://github.com/JiuNian3219/architext/tree/main/templates/zh/skills/archi-decompose-roadmap
Command: npx skills add https://github.com/JiuNian3219/architext --skill archi-decompose-roadmap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architext's roadmap decomposition translates vague briefs into a structured set of Infra, Feature, Polish, and Edit tasks with clear DoD and dependencies, enabling consistent planning and execution.

Core Features & Use Cases

  • Converts briefs into Tier 1 Roadmap JSON with phase-separated tasks (INF-xx / FEAT-xx / POLISH-xx / EDIT-xx).
  • Builds dependencies graphs, identifies real-world task relationships, and exports to /archi.plan inputs.
  • Supports five-step decomposition (project calibration, dual perspective Task/Infra extraction, Polish injection, NFR weighting, and real dependency chains) to drive parallel execution.

Quick Start

Provide a project brief and run /archi.scope to generate a draft roadmap.

Frequently Asked Questions about archi-decompose-roadmap

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

FAQPage Schema
How do I decompose a project brief into structured roadmap tasks with dependencies?

Roadmap task decomposition translates briefs into phase-separated tasks (INF-XX, FEAT-XX, POLISH-XX) with dependencies. It uses a five-step process for infra scaffolding, core features, and polish tasks, outputting validated JSON for parallel execution.

What is the best way to structure an architecture-driven roadmap for parallel execution?

To structure an architecture-driven roadmap, decompose briefs into phase-separated tasks with enforced ID prefixes and real dependency chains. Identifying these task relationships builds dependency graphs that output parallel-executable batches for infra, features, and polish phases.

How do I identify real dependencies between infrastructure and feature tasks during planning?

Identifying dependencies between infra and feature tasks uses dual perspective Task and Infra extraction. This builds dependency graphs identifying real-world task relationships to drive parallel execution across roadmap phases.

Can I generate a JSON roadmap output from a project brief for downstream planning tools?

Yes, generating a canonical roadmap JSON from project briefs for downstream planning is supported. The decomposition outputs a Tier 1 schema validated JSON containing structured tasks and dependencies to feed archi.plan inputs.

Does roadmap decomposition enforce specific phase requirements like infra scaffolding and feature development?

Roadmap decomposition enforces strict Phase 1 Infra scaffolding, Phase 2 Core Features, and Phase 3 Polish requirements. It applies ID prefixes and dependencies to satisfy these phases within the Tier 1 schema validated output.

When do I need to inject non-functional requirements into a task decomposition roadmap?

Non-functional requirement injection is needed during the five-step roadmap decomposition process. It applies NFR weighting after dual perspective Task and Infra extraction to ensure architecture-driven product planning meets quality standards.