skills.rest
robkam
robkamCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

architect-planning

Translate architectural requests into concrete design tasks with files, risks, invariants, and acceptance criteria.

12|1|Updated Oct 31, 2025
Search Tags:#planning#architecture#requirements#handoffs#architect#risks
One-click install
npx skills add https://github.com/robkam/ytreenova --skill architect-planning
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architect-planning
Source: https://github.com/robkam/ytreenova/tree/main/.ai/skills/architect-planning
Command: npx skills add https://github.com/robkam/ytreenova --skill architect-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan architectural changes by translating requests into concrete design tasks, including files, risks, invariants, and acceptance criteria.

Core Features & Use Cases

  • Structured design tasks: Convert high-level requests into actionable work items with traceable changes.
  • Risk & invariant capture: Identify risks and invariants to guard architectural integrity.
  • Handoff-ready artifacts: Produce a minimal, atomic change plan and documentation suitable for developer handoff.

Quick Start

Provide a minimal, atomic plan to implement the requested architectural change, including required files, risks, invariants, and acceptance criteria.

Frequently Asked Questions about architect-planning

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

FAQPage Schema
How do I plan architectural changes with clear developer handoffs?▼

Plan architectural changes by translating requests into a minimal, atomic change plan that includes required files, risks, invariants, and acceptance criteria. This provides structured, handoff-ready artifacts for developers.

What is an atomic change plan in software architecture?▼

An atomic change plan in software architecture is a minimal, actionable design task breakdown. It specifies which files to modify, context files, acceptance criteria, risks, and invariants to guard architectural integrity during implementation.

How do I translate high-level requirements into actionable design tasks?▼

Translate high-level requirements into actionable design tasks by structuring the work into traceable changes. Specify the exact files to modify, identify potential risks, define invariants, and establish clear acceptance criteria for developer handoff.

Can I use this approach for architecture-level requests impacting technical strategy?▼

Yes, you can use this approach for architecture-level requests impacting technical strategy. It processes requests affecting behavior and implementation details, converting them into a documented plan with traceable design tasks and risk capture.

Why do I need to identify risks and invariants before an architectural change?▼

You need to identify risks and invariants before an architectural change to guard architectural integrity. Capturing these elements ensures that the minimal change plan respects existing system constraints and meets defined acceptance criteria.

Related Skills

Explore More Software Engineering Skills→
shafibabarshafibabar
1

system-context-diagram

Creates a C4 Level 1 System Context Diagram identifying human actors and external system dependencies.

Community
Intermediate
benredmondbenredmond
3

implement

Translate plans into runnable code and validate against acceptance criteria.

Community
Advanced
skogaiskogai

explore-codebase

Map codebase relationships between functions, classes, and modules using knowledge graph tools.

Official
Intermediate
ajayjoshi-ciphersonicajayjoshi-ciphersonic

plan

Create structured Markdown project plans without modifying existing files.

Community
Basic