skills.rest
alex-voloshin-dev
alex-voloshin-devCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

plan

Decompose feature requirements into role-specific work packages with multi-reviewer architectural approval.

2|Updated Mar 19, 2026
Search Tags:#workflow#planning#architecture#review#engineering#feature-development
One-click install
npx skills add https://github.com/alex-voloshin-dev/ai-skills --skill plan-alex-voloshin-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/alex-voloshin-dev/ai-skills/tree/main/.windsurf/skills/plan
Command: npx skills add https://github.com/alex-voloshin-dev/ai-skills --skill plan-alex-voloshin-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of poorly defined feature requirements and architectural misalignment by enforcing a structured, multi-reviewer planning process before any code is written.

Core Features & Use Cases

  • Structured Decomposition: Breaks down complex features into service-level and role-specific work packages with clear dependencies.
  • Multi-Reviewer Feedback Loop: Mandates approval from product, solution, and system architects to ensure end-to-end design coherence.
  • Risk Assessment: Identifies potential bottlenecks, breaking changes, and integration risks early in the development lifecycle.

Quick Start

Run the plan skill by providing the path to your feature brief or PRD to initiate the architectural decomposition and review process.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I decompose complex feature requirements into actionable work packages?▼

Feature decomposition breaks complex requirements into role-specific work packages across service boundaries. This process clarifies dependencies and structural alignment before any implementation begins.

How does the multi-reviewer architectural feedback loop work?▼

The multi-reviewer feedback loop mandates approval from product, solution, and system architects. This ensures technical feasibility, end-to-end design coherence, and risk mitigation before development starts.

What is the best way to ensure architectural alignment before implementation begins?▼

Architectural alignment is achieved by enforcing a structured planning process that decomposes features into service-level packages. This mandates multi-reviewer approval to ensure end-to-end design coherence.

How do I identify integration risks and breaking changes early in the development lifecycle?▼

Identifying integration risks early involves a structured planning process that assesses potential bottlenecks and breaking changes. This mitigation happens before code is written through architectural review.

Can I use this planning process with an existing product requirements document (PRD)?▼

Yes, the planning process accepts an existing product requirements document or feature brief as input. Providing the PRD path initiates the architectural decomposition and multi-reviewer cycle.

When do I need a structured feature decomposition process for software engineering?▼

A structured feature decomposition process is needed when facing poorly defined requirements and architectural misalignment. It enforces multi-reviewer planning to mitigate technical risks before coding starts.

Related Skills

Explore More Software Engineering Skills→
Reading-Advantage-ThailandReading-Advantage-Thailand

prd-authoring

Generate and validate PRD drafts using the Gemini CLI.

Official
Advanced
HellblazerHellblazer
4

java-development

Delegate plan-approved Java implementation tasks to the java-developer agent.

Community
Intermediate
mkusakamkusaka
7

code-review-phase-0-gather-the-diff

Retrieve unified diffs from git repositories for code review.

Community
Basic
nguyenthienthanhnguyenthienthanh
24

pm-expert

Guide Agile project planning with estimation, risk, and stakeholder management.

Community
Basic