analysis

Create Czech-language technical analysis documents with architecture and risk assessment.

7|1|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/cloudfieldcz/cf-powers --skill analysis-cloudfieldcz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analysis
Source: https://github.com/cloudfieldcz/cf-powers/tree/main/skills/analysis
Command: npx skills add https://github.com/cloudfieldcz/cf-powers --skill analysis-cloudfieldcz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turns vague ideas into a structured, Czech-language technical analysis document.

Core Features & Use Cases

  • Guides from idea to a formal architecture and risk analysis.
  • Generates a phase-based implementation plan with cross-check readiness.
  • Outputs to docs/plans/YYYY-MM-DD-<topic>.md for reproducible handoffs.

Quick Start

Provide a vague feature idea and I will generate a Czech technical analysis ready for planning.

Frequently Asked Questions about analysis

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

FAQPage Schema
How do I turn a vague feature idea into a structured technical analysis document?

To turn a vague idea into a technical analysis, provide the initial concept to generate a structured document. This process transforms early-stage features into formal architecture reviews, risk assessments, and phase-based implementation plans with cross-check readiness.

What should a technical analysis include for early-stage architecture planning?

A technical analysis for early-stage architecture planning should include an architecture overview, phase breakdown, data changes, testing considerations, and risk assessment. It provides cross-check planning to ensure a ready-to-implement analysis for formal review.

How do I generate a phase-based implementation plan from a rough concept?

You generate a phase-based implementation plan by submitting your rough concept for structured analysis. The process evaluates architecture and risks, outputting a detailed plan with cross-check readiness and testing considerations to guide subsequent development.

Can I output technical analysis documents to a deterministic file path for reproducible handoffs?

Yes, you can output technical analysis documents to a deterministic file path for reproducible handoffs. The generated analysis is saved under docs/plans/YYYY-MM-DD-<topic>.md, ensuring consistent documentation and easy retrieval for architecture reviews.

Does the generated technical analysis include risk assessment and cross-check planning?

Yes, the generated technical analysis includes comprehensive risk assessment and cross-check planning. It transforms early-stage ideas into ready-to-implement documents by evaluating potential risks and detailing testing considerations alongside the architecture overview.

When do I need a formal technical analysis before starting software implementation?

You need a formal technical analysis before starting software implementation when transitioning from a vague idea to a structured plan. It is essential for early-stage features requiring architecture review, phase breakdown, and data change evaluation to ensure cross-check readiness.