expand

Updates VISION.md, SPEC.md, ARCHITECTURE.md, and roadmap for project expansions.

7|4|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/nklisch/skills --skill expand-nklisch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: expand
Source: https://github.com/nklisch/skills/tree/main/plugins/workflow/skills/expand
Command: npx skills add https://github.com/nklisch/skills --skill expand-nklisch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The expand skill helps teams broaden a project's scope by systematically updating its core foundation documents—VISION.md, SPEC.md, ARCHITECTURE.md, and the roadmap—so that subsequent design phases can incorporate major new capabilities or subsystems.

Core Features & Use Cases

  • Document Analysis: Reads all existing foundation docs and the current roadmap to establish a baseline.
  • Codebase Mapping: Explores the current code structure to understand built modules and patterns.
  • User Interview: Guides a conversation to capture the desired expansion, assessing impact on architecture, specs, and vision.
  • Impact Assessment: Evaluates how the expansion affects architecture, specifications, vision, and roadmap.
  • Targeted Updates: Edits the relevant foundation documents incrementally, preserving unchanged content and marking new sections.
  • Roadmap Integration: Adds new phases for the expansion and aligns them with existing work.

Quick Start

Use the expand skill to incorporate a new payment processing subsystem into the project's foundation documents.

Frequently Asked Questions about expand

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

FAQPage Schema
How do I update foundation documents when adding major new capabilities to my project?

To update foundation documents for major new capabilities, the project scope is expanded by reading VISION.md, SPEC.md, ARCHITECTURE.md, and the roadmap, then editing them to reflect the new subsystems or architectural shifts.

When do I need to update my project roadmap and architecture for a new subsystem?

You need to update your project roadmap and architecture when adding major capabilities, new subsystems, or architectural shifts beyond small feature additions, ensuring the expansion is systematically integrated into the baseline.

What is the best way to assess the impact of a new subsystem on existing project specifications?

The best way to assess impact on existing project specifications is through a guided user interview that evaluates how the expansion affects the architecture, specifications, vision, and roadmap before making targeted updates.

Can I integrate a payment processing subsystem into my existing architecture and roadmap?

Yes, you can integrate a payment processing subsystem by analyzing the current code structure, assessing its impact on the vision and specifications, and adding new roadmap phases aligned with existing work.

How do I preserve unchanged content in VISION.md and SPEC.md while documenting an architectural shift?

To preserve unchanged content during an architectural shift, the relevant foundation documents are edited incrementally, keeping existing sections intact while clearly marking the new sections that reflect the expansion.