skills.rest
flight505
flight505COMMUNITY
Explore all skills by this author →
WebsiteGitHub

building-blocks

Decompose software projects into buildable blocks with interfaces and dependencies.

4|Updated Jan 6, 2026
Search Tags:#architecture#dependency graph#incremental delivery#building blocks#component specification#interface contracts
One-click install
npx skills add https://github.com/flight505/claude-project-planner --skill building-blocks-flight505
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: building-blocks
Source: https://github.com/flight505/claude-project-planner/tree/main/project_planner/.claude/skills/building-blocks
Command: npx skills add https://github.com/flight505/claude-project-planner --skill building-blocks-flight505

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Building blocks enable teams to break complex software projects into discrete, independently buildable components, with clear interfaces, dependencies, and acceptance criteria.

Core Features & Use Cases

  • Component-based decomposition: define interfaces, responsibilities, and integration contracts.
  • Dependency graph planning: map internal/external dependencies and plan build order.
  • Incremental delivery governance: estimate effort, align with sprints, and enable iterative releases.

Quick Start

Create a master list of blocks, define at least BB-001, BB-002 with name, id, type, description, dependencies, interfaces, complexity, estimates, and test criteria. Then generate a simple DAG showing dependencies and draft an initial build-order plan.

Frequently Asked Questions about building-blocks

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

FAQPage Schema
How do I decompose software into buildable blocks for incremental delivery?▼

Software decomposition into buildable blocks involves defining discrete components, interface contracts, and dependency graphs, enabling incremental delivery and iterative releases across cross-functional teams.

What is the best way to map a dependency graph for component-based architecture?▼

Mapping a dependency graph for component-based architecture requires listing internal and external dependencies for each block, then generating a DAG to establish a valid build order and integration sequence.

How do I define interface contracts for software components?▼

Defining interface contracts for software components requires specifying block identity, type, responsibilities, and test criteria, ensuring clear integration boundaries and governance metadata for cross-functional teams.

Can I use component decomposition to plan sprint estimates and effort?▼

Yes, component decomposition supports sprint planning by providing effort estimates, complexity ratings, and test criteria for each block, aligning incremental delivery governance with iterative release schedules.

What metadata do I need to define a building block for architecture planning?▼

Defining a building block for architecture planning requires metadata including a unique ID, name, type, description, dependencies, interfaces, complexity rating, effort estimates, and acceptance test criteria.

Why does incremental delivery require a dependency graph and build order plan?▼

Incremental delivery requires a dependency graph and build order plan to sequence component integration correctly, preventing bottlenecks and ensuring that interface contracts are satisfied before downstream development.

Related Skills

Explore More Software Engineering Skills→
vinvcnvinvcn
23

spec-driven-development

Generate a project specification before implementing new features.

Community
Advanced
Emz1998Emz1998
1

agile-planning

Generate agile release plans with sprint schedules, task codes, and roadmaps.

Community
Basic
pkuppenspkuppens

v-model-design-verification

Verify APIs, data schemas, and module contracts against design specifications.

Community
Advanced
Fantasia1999Fantasia1999

senior-architect

Generate Mermaid, PlantUML, or ASCII architecture diagrams and analyze dependencies.

Community
Advanced