apex-input-analysis

Analyzes project input documents to extract structured requirements and normalize them for planning.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/JaviMontano/metodologia-propuesta-agent-public --skill apex-input-analysis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: apex-input-analysis
Source: https://github.com/JaviMontano/metodologia-propuesta-agent-public/tree/main/.claude/skills/discovery/input-analysis
Command: npx skills add https://github.com/JaviMontano/metodologia-propuesta-agent-public --skill apex-input-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill converts unstructured project input materials (briefs, RFPs, SOWs, emails, and meeting notes) into a normalized, structured digest that supports chartering and planning. It identifies objectives, constraints, stakeholders, assumptions, and key decisions, and it flags contradictions and gaps across documents to improve decision quality.

Core Features & Use Cases

  • Document inventory and metadata extraction from input sources.
  • Requirement extraction (explicit and implicit) and stakeholder mapping.
  • Contradiction detection, gap analysis, and assumption tagging to surface risks early.
  • Normalize outputs into a consistent input digest for planning, governance, and kickoffs.
  • Use Case: Prepare a project charter from scattered inputs and surface missing information for stakeholder review.

Quick Start

Run the apex-input-analysis skill on a folder of project inputs to generate a structured input digest ready for planning.

Frequently Asked Questions about apex-input-analysis

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

FAQPage Schema
How do I extract structured requirements from unstructured project briefs and RFPs?

Contradiction detection during document analysis compares multiple project inputs to surface conflicting requirements and assumptions. It identifies gaps across briefs, SOWs, and meeting notes, flagging missing information early so teams can address risks before project kickoff.

What is the best way to normalize scattered project inputs for chartering and planning?

Normalizing scattered project inputs for chartering involves processing multi-document sets to extract metadata, map stakeholders, and tag assumptions. This produces an organized input digest that standardizes unstructured materials into a structured format ready for governance and planning activities.

Can I use input analysis for multi-document sets like emails and meeting notes?

Input analysis supports multi-document sets including emails, meeting notes, briefs, and SOWs. It performs document inventory and metadata extraction across all sources, ensuring that implicit requirements and stakeholder details from varied formats are captured in the final normalized digest.

How do I prepare a project charter from fragmented stakeholder inputs?

Preparing a project charter from fragmented stakeholder inputs requires consolidating scattered documents into a structured digest. By extracting objectives, identifying stakeholders, and flagging missing information, the analysis creates a normalized foundation that supports charter creation and stakeholder review.

Does input analysis identify gaps and missing information across project documents?

Input analysis identifies gaps and missing information across project documents by comparing requirements from multiple sources. It tags assumptions and detects contradictions between briefs, RFPs, and SOWs, surfacing incomplete data that requires stakeholder clarification before planning proceeds.