project-teardown

Decompose software project architectures into structured metadata bundles.

29|7|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/Yirzzzz/project-teardown-skill --skill project-teardown
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-teardown
Source: https://github.com/Yirzzzz/project-teardown-skill/tree/main
Command: npx skills add https://github.com/Yirzzzz/project-teardown-skill --skill project-teardown

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and decompose software projects' architectures into structured metadata to support discovery, governance, and architectural learning.

Core Features & Use Cases

  • Progressive teardown: first provide a global overview, then progressively dive into dimensions such as concurrency, caching, data storage, RAG, context, memory, tool calling, async tasks, observability, permissions, multi-user isolation, middleware, configuration management, deployment boundaries, evaluation, and scaling bottlenecks.
  • Metadata generation: output structured fields including name, tagline, description, request, complexity, category, keywords, dependencies, components, and toxicity_check.
  • Reusable artifact: architecture.md style documentation to support traceable teardown records.

Quick Start

Provide a global overview first, then progressively drill into core architectural dimensions.

Frequently Asked Questions about project-teardown

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

FAQPage Schema
How do I decompose a software project architecture into structured metadata?

To decompose a software project architecture, you systematically teardown the system to generate a metadata bundle including name, tagline, description, complexity, keywords, dependencies, and components. This enforces a YAML frontmatter standard.

What is the best way to analyze RAG and agent system architectures?

Analyzing RAG and agent system architectures is best done through progressive teardown, starting with a global overview and then diving into specific dimensions like context, memory, tool calling, and retrieval pipelines.

Can I generate architecture documentation for governance and traceability?

Yes, you can generate architecture.md style documentation to support traceable teardown records. This reusable artifact provides global overviews and iterative deep-dives to support architectural learning and governance.

What architectural dimensions should I evaluate when analyzing backend systems?

When analyzing backend systems, evaluate architectural dimensions like concurrency, caching, data storage, async tasks, observability, permissions, multi-user isolation, middleware, and deployment boundaries.

Does this metadata generation process work for mature systems with complex dependencies?

Yes, this metadata generation process specifically applies to mature backend, agent, and RAG systems. It handles complex dependencies by iteratively drilling into core architectural dimensions to reveal scaling bottlenecks.