platform-spec

Guide Platform Architects through creating a complete Platform Spec with SpecKit and MCP.

Updated Feb 5, 2026
One-click install
npx skills add https://github.com/javierhbr/agnostic-agent-loop --skill platform-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: platform-spec
Source: https://github.com/javierhbr/agnostic-agent-loop/tree/main/internal/skills/packs/sdd/platform-spec
Command: npx skills add https://github.com/javierhbr/agnostic-agent-loop --skill platform-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill guides Platform Architects in creating comprehensive Platform Specifications, ensuring alignment with architectural principles and business objectives.

Core Features & Use Cases

  • Structured Spec Creation: Follows a step-by-step workflow to define problem statements, domain models, UX flows, contracts, and NFRs.
  • Architectural Guidance: Ensures specs are grounded in the Constitution and MCP, facilitating cross-domain initiatives.
  • Use Case: When initiating a new cross-domain feature, use this Skill to systematically document its requirements, impact, and integration points, ensuring all stakeholders have a clear understanding.

Quick Start

Use the platform-spec skill to start creating a new Platform Feature Spec for the initiative ECO-124.

Frequently Asked Questions about platform-spec

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

FAQPage Schema
How do I create a platform specification for cross-domain initiatives?

To create a platform specification for cross-domain initiatives, you follow a structured workflow that defines problem statements, domain models, UX flows, contracts, and NFRs guided by architectural principles.

What should a complete platform spec include for component teams?

A complete platform spec should include problem definition, domain modeling, UX design, contract specification, and NFR declaration to ensure component teams understand integration points and requirements.

How does MCP integrate with platform specification and architectural guidelines?

MCP integrates with platform specification by grounding the document creation process in architectural guidelines, ensuring cross-domain initiatives align with the Constitution and facilitating stakeholder alignment.

Can I use SpecKit to document requirements for a new cross-domain feature?

Yes, you can use SpecKit to document requirements for a new cross-domain feature by systematically defining its impact, integration points, and architectural grounding within a structured platform spec.

What is the best way to structure non-functional requirements in a platform spec?

The best way to structure non-functional requirements in a platform spec is to declare them alongside domain models and contracts, ensuring they adhere to established architectural guidelines for component teams.

When do I need to define domain models and UX flows in platform documentation?

You need to define domain models and UX flows in platform documentation when initiating a new cross-domain feature, ensuring all stakeholders have a clear understanding of requirements and integration points.