analysis-design

Define analysis scope, objectives, constraints, and success criteria with evidence and risk assessment.

4|Updated Sep 6, 2013
One-click install
npx skills add https://github.com/mway/dotfiles --skill analysis-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analysis-design
Source: https://github.com/mway/dotfiles/tree/main/home/dot_codex/skills/analysis-design
Command: npx skills add https://github.com/mway/dotfiles --skill analysis-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured framework and workflow for performing rigorous analysis, audits, and design reasoning with evidence-based methods, improving clarity, traceability, and decision quality.

Core Features & Use Cases

  • Scoped analysis design that defines objectives, constraints, and success criteria.
  • Evidence collection guidelines, references, and verification status for each claim.
  • Scenario and edge-case enumeration with a risk and feasibility assessment.
  • Recommendations plan, risk register, and verification strategy for follow-up actions.
  • Use Case: An analyst conducts requirements analysis for a new system architecture and produces a traceable decision record.

Quick Start

Follow the 5-phase problem-solving framework and the listed reference materials to configure and execute the analysis task.

Frequently Asked Questions about analysis-design

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

FAQPage Schema
How do I structure requirements analysis for a new system architecture?

Requirements analysis requires defining scope, objectives, constraints, and success criteria. You enumerate scenarios, gather evidence from reference materials, and produce a traceable decision record with a prioritized recommendations plan and risk register.

What is the best way to perform evidence-based risk analysis for complex decisions?

Evidence-based risk analysis involves assessing scenario coverage and feasibility with explicit verification status for each claim. This structured approach yields a risk register and verification strategy, improving clarity and decision quality for follow-up actions.

How do I enumerate edge cases and scenarios during an audit or design reasoning task?

Scenario enumeration requires listing edge cases, gathering supporting evidence from reference materials, and assessing coverage. Each scenario receives a feasibility assessment and explicit verification status to ensure traceable design reasoning.

Can I use a structured problem-solving framework to generate a risk register and verification strategy?

Yes, a structured problem-solving framework guides you through scoping, evidence collection, and risk assessment to generate a risk register. It also produces a verification strategy and recommendations plan with prioritized actions.

What are the limitations of unstructured analysis compared to a scoped analysis design?

Unstructured analysis lacks traceable decision records, explicit verification status, and defined success criteria. A scoped analysis design mitigates these limitations by enforcing evidence collection guidelines and a structured recommendations plan.

Does structured analysis design work for auditing existing systems and architectures?

Yes, structured analysis design supports rigorous audits by defining constraints and success criteria, gathering evidence, and assessing risks. It outputs a verification strategy and prioritized actions for system architecture improvements.