plan-analyzer

Parse plan.md to extract architectural decisions and validate technical configurations.

Updated May 18, 2026
One-click install
npx skills add https://github.com/fzturk/clearlegaltips-workspace --skill plan-analyzer-fzturk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-analyzer
Source: https://github.com/fzturk/clearlegaltips-workspace/tree/main/.claude/skills/plan-analyzer
Command: npx skills add https://github.com/fzturk/clearlegaltips-workspace --skill plan-analyzer-fzturk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the deep analysis of system plans, extracting architectural decisions, constraints, technology stacks, forbidden items, data flows, and governance requirements to facilitate comprehensive documentation generation.

Core Features & Use Cases

  • Deep Plan Analysis: Extracts detailed information from plan.md files to drive document generation.
  • Input/Output Handling: Processes plan.md and outputs structured reports for downstream generators.
  • Use Case: After finalizing a system plan, use this skill to automatically generate an analysis report that guides the documentation creation process.

Quick Start

Annotate your system plan in 'plan.md' and execute 'analyze plan --source plan.md' to produce a structured analysis report.

Frequently Asked Questions about plan-analyzer

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

FAQPage Schema
How do I automate system architecture analysis from a markdown plan file?

To automate system architecture analysis, you parse a 'plan.md' file to extract architectural decisions, constraints, and technology stacks, generating a structured report that guides downstream documentation generation.

What is plan parsing for document automation and when is it needed?

Plan parsing for document automation is the process of identifying architectural decisions and validating technical configurations from system plans. You need it when finalizing a system plan to automatically drive comprehensive documentation creation.

How do I extract data flows and technology stacks from system documentation?

You extract data flows and technology stacks from system documentation by running an automated deep analysis on the specified 'plan.md' file, which identifies and structures these technical configurations into a comprehensive report.

Does the plan analyzer work with standard markdown files for technology assessment?

Yes, the plan analyzer works with standard markdown files for technology assessment by processing a 'plan.md' file to validate technical configurations and identify governance requirements, outputting a structured analysis report.

What is the best way to generate structured reports from system plans?

The best way to generate structured reports from system plans is to execute an automated deep analysis command on your 'plan.md' file, which extracts forbidden items, constraints, and data flows to produce a structured output for downstream generators.

What are the limitations of automated plan parsing for system documentation?

A limitation of automated plan parsing is that it requires the system plan to be specifically annotated in a 'plan.md' file format to successfully extract architectural decisions and validate technical configurations for the analysis report.