factory-analysis

Analyze codebases against requirements and propose three scored implementation approaches.

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/JongHyunLee84/factory --skill factory-analysis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: factory-analysis
Source: https://github.com/JongHyunLee84/factory/tree/main/skills/factory-analysis
Command: npx skills add https://github.com/JongHyunLee84/factory --skill factory-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps you understand the current state of your codebase, pinpoint discrepancies between requirements and implementation, and evaluate different approaches for building new features or refactoring existing ones.

Core Features & Use Cases

  • Codebase Survey: Scans your project to identify existing files, modules, and conventions.
  • Requirements Feasibility: Assesses how well your current code meets defined requirements, flagging gaps.
  • Implementation Options: Generates 3 distinct, scored approaches (Extend Existing, New Module, Hybrid) for implementing a feature, detailing effort, risk, and maintainability.
  • Escalation Checklist: Flags critical architectural changes, external dependencies, or security/performance impacts for user review.
  • Duplication Check: Evaluates new components against existing code to identify potential reuse opportunities.

Quick Start

Use the factory-analysis skill to analyze the current codebase and identify implementation options for a new user authentication feature.

Frequently Asked Questions about factory-analysis

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

FAQPage Schema
How do I identify gaps in my codebase against new software requirements?

Gap analysis scans existing files and modules to pinpoint discrepancies between requirements and implementation. It evaluates feasibility, detects duplication, and flags architectural concerns, providing evidence-based options for resolving missing functionality.

What is the best way to evaluate implementation options for a new software feature?

Evaluating implementation options involves generating three distinct, scored approaches: Extend Existing, New Module, and Hybrid. Each approach details effort, risk, and maintainability trade-offs to help you choose the most viable strategy for your codebase.

How do I check for code duplication before adding a new component?

Duplication detection evaluates new components against existing code to identify potential reuse opportunities. By scanning project conventions and modules, it flags overlapping functionality to prevent redundant implementations and maintain architectural consistency.

Can I assess the feasibility of extending an existing software architecture without breaking it?

Feasibility assessment evaluates how well current code meets defined requirements and flags critical architectural changes. It generates an escalation checklist for security, performance impacts, and external dependencies to review before modifying the architecture.

When do I need an architectural escalation checklist for my development project?

An escalation checklist is needed when gap analysis flags critical architectural changes, external dependencies, or security and performance impacts. It ensures these high-risk modifications are reviewed before proceeding with the chosen implementation strategy.