spec-implementing-analyzing

Name: spec-implementing-analyzing
Availability: InStock
Author: kaptinlin

Analyze SPECS/*.md and existing code to generate a project-root ANALYSIS.md.

23|2|Updated Jun 9, 2025

Search Tags:#workflow #planning #documentation #analysis #specs #module-structure

Ready to run

npx skills add https://github.com/kaptinlin/gozod --skill spec-implementing-analyzing

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-implementing-analyzing
Source: https://github.com/kaptinlin/gozod/tree/main/.agents/skills/spec-implementing-analyzing
Command: npx skills add https://github.com/kaptinlin/gozod --skill spec-implementing-analyzing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

An organized method to translate approved SPECS into a concrete implementation plan by analyzing documentation and existing code to surface scope, priorities, and module structure.

Core Features & Use Cases

Systematic SPECS analysis to generate a root ANALYSIS.md defining implementation scope and module boundaries.
Prioritization guidance and category mapping to guide Stage 3 planning before task generation.
Maintains traceability from SPECS to the resulting ANALYSIS.md to support review and alignment.

Quick Start

Invoke this skill to analyze SPECS and existing code to produce ANALYSIS.md at the project root.

Frequently Asked Questions about spec-implementing-analyzing

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

FAQPage Schema

How do I translate approved specifications into a concrete implementation plan?▼

To translate approved specifications into an implementation plan, analyze SPECS/*.md files alongside existing code to generate a root ANALYSIS.md defining scope, priorities, and module structure. This enforces traceability from specifications to categories before task generation.

What is the best way to analyze project specs and existing code for module structure?▼

Analyzing project specs and existing code for module structure involves reading SPECS/*.md files to surface boundaries and priorities, then generating an ANALYSIS.md document. This structured plan maps modules and categories to support review before development begins.

How do I determine what to build and in what order from approved specifications?▼

Determining build order from approved specifications requires analyzing documentation to surface priorities and scope. Generating an ANALYSIS.md file provides prioritization guidance and category mapping to sequence implementation tasks effectively.

When do I need to generate an implementation scope analysis from SPECS?▼

Generate an implementation scope analysis from SPECS when starting Stage 3 implementation from approved specifications. It determines what to build, module relationships, and boundaries, producing a structured plan suitable for review before task generation.

Does this specs analysis workflow maintain traceability from documentation to implementation categories?▼

Yes, the specs analysis workflow maintains traceability from documentation to implementation categories. It maps SPECS/*.md files directly to the resulting ANALYSIS.md, ensuring alignment and supporting structured review before generating development tasks.