architect

Generate sprint-based technical plans with task decomposition and risk identification.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/scottymcandrew/the-promptorium-scottys-archive-of-ai-chaos --skill architect-scottymcandrew
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/scottymcandrew/the-promptorium-scottys-archive-of-ai-chaos/tree/main/claude-skills/architect
Command: npx skills add https://github.com/scottymcandrew/the-promptorium-scottys-archive-of-ai-chaos --skill architect-scottymcandrew

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps break down large, complex requirements into manageable, actionable tasks for software development sprints, reducing ambiguity and identifying risks early.

Core Features & Use Cases

  • Requirements Analysis: Extracts explicit and implicit needs from PRDs.
  • Task Decomposition: Breaks down features into 1-3 day tasks with clear acceptance criteria.
  • Risk Management: Identifies and assesses potential risks with mitigation and contingency plans.
  • Use Case: When starting a new feature, use this Skill to generate a technical plan that outlines backend and frontend tasks, integration points, and sprint goals.

Quick Start

Use the architect skill to create a technical plan for the new user authentication feature.

Frequently Asked Questions about architect

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

FAQPage Schema
How do I break down complex software requirements into actionable sprint tasks?

Task decomposition analyzes software requirements to break down complex features into 1-3 day actionable sprint tasks. It extracts explicit and implicit needs from PRDs to define clear acceptance criteria and reduce ambiguity for development teams.

What is the best way to plan technical architecture for a new frontend and backend feature?

Technical architecture planning generates detailed plans by separating frontend and backend tasks, sequencing dependencies, and defining integration points. This approach reduces ambiguity and enables confident team execution across agile development sprints.

How do I identify and assess technical risks when planning a new software feature?

Risk assessment identifies and evaluates potential technical risks during software feature planning. It generates mitigation and contingency plans early in the sprint planning phase to reduce ambiguity and prevent execution blockers.

Can I generate agile sprint goals and acceptance criteria from a product requirements document?

Yes, requirements analysis extracts explicit and implicit needs from PRDs to generate sprint goals and acceptance criteria. This task decomposition process ensures large software features are broken down into manageable, confidently executable work items.

Does this task planning approach work for managing dependencies in agile development?

Dependency sequencing supports agile development by mapping integration points and ordering frontend and backend tasks. This technical planning process ensures sprint tasks are properly sequenced, reducing ambiguity and enabling confident team execution.