terrarium-analyze

Scopes task impact and identifies affected files for Terrarium projects.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/kunho817/Terrarium --skill terrarium-analyze
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: terrarium-analyze
Source: https://github.com/kunho817/Terrarium/tree/main/.claude/skills/terrarium-analyze
Command: npx skills add https://github.com/kunho817/Terrarium --skill terrarium-analyze

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Terrarium Analyze skill provides a frozen architecture map of the Terrarium project to help you scope task impact, identify affected files, and prepare context for downstream agents.

Core Features & Use Cases

  • Architecture map snapshot for quick task scoping.
  • Domain classification to determine project areas affected by a change.
  • Subagent prompt templates to dispatch context-aware workers without rereading code.
  • Use cases include starting a feature, triaging bugs, and planning large refactors.
  • Supports rapid context provisioning for architecture-aware planning.

Quick Start

Generate the architecture map and domain classification for the current Terrarium task, then dispatch context-aware subagents.

Frequently Asked Questions about terrarium-analyze

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

FAQPage Schema
How do I scope task impact and identify affected files before starting a new feature?

To scope task impact, you can generate a frozen architecture map and domain classification to map blast radii and identify affected files. This provides context-aware planning before dispatching downstream workers.

How do I dispatch context-aware subagents without rereading the entire codebase?

You can dispatch context-aware subagents by using pre-built subagent prompt templates. These templates provision rapid context, allowing workers to execute tasks without rereading code.

What is a frozen architecture map and when do I need it for project planning?

A frozen architecture map is a snapshot of project structure used for quick task scoping. You need it when starting features, triaging bugs, or planning large refactors to understand domain classification.

Can I use architecture mapping to triage bugs and plan large refactors?

Yes, architecture mapping supports bug triaging and large refactor planning by providing a domain classification snapshot. This helps determine project areas affected by a change.

Does this architectural analysis approach work without external dependencies?

Yes, this architectural analysis approach works without external dependencies. It relies entirely on an internal frozen architecture map and subagent prompt templates to guide planning and execution.

Best way to provision rapid context for architecture-aware planning?

The best way to provision rapid context for architecture-aware planning is generating an architecture map snapshot alongside subagent prompt templates. This prepares context for downstream agents quickly.