skills.rest
cspergel
cspergelCOMMUNITY
Explore all skills by this author →
GitHub

specification

Create 14-field ForgePlan node specifications with validation rules.

Updated Apr 4, 2026
Search Tags:#validation#acceptance-criteria#shared-models#spec-template#quality-rules#node-spec
One-click install
npx skills add https://github.com/cspergel/forgedev --skill specification-cspergel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: specification
Source: https://github.com/cspergel/forgedev/tree/main/skills/specification
Command: npx skills add https://github.com/cspergel/forgedev --skill specification-cspergel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, standardized approach for creating high-quality node specifications within ForgePlan, ensuring consistency, completeness, and alignment with the manifest and shared-model rules across teams.

Core Features & Use Cases

  • Node Spec Template: The ForgePlan 14-field node spec template enforces a consistent schema for every node, including fields like node, name, description, inputs, outputs, shared_dependencies, data_models, interfaces, acceptance_criteria, constraints, non_goals, failure_modes, file_scope, and depends_on.
  • Quality Rules: Acceptance criteria must include a test field; each node must have at least one non_goal and at least one failure_mode; shared_dependencies must reference manifest-defined shared models; file_scope must be unique across nodes; interfaces must specify directional types.
  • Shared Model Rules: Shared models are defined in the manifest and referenced via $shared. Any entity used by multiple nodes must be declared as a shared model in the manifest.

Quick Start

Create a complete node specification using the 14-field template and validate it against the manifest rules.

Frequently Asked Questions about specification

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

FAQPage Schema
How do I create machine-checkable node specifications for consistent schema validation?▼

To create machine-checkable node specifications, use a 14-field template enforcing schema consistency. This standardizes node design across teams by validating inputs, outputs, and shared dependencies against defined manifest rules.

What quality rules are required for acceptance criteria in a node spec template?▼

Acceptance criteria in a node spec template must include a specific test field. Additionally, every node requires at least one defined non_goal and one failure_mode to pass validation and ensure complete quality rules.

How do shared model references align with the manifest when building node specs?▼

Shared model references align with the manifest by declaring any entity used across multiple nodes as a shared model. These are referenced via $shared, ensuring shared_dependencies strictly match manifest-defined models.

Does node specification validation enforce unique file_scope and directional interface types?▼

Yes, node specification validation enforces unique file_scope across all nodes and requires interfaces to specify directional types. This ensures strict governance and prevents overlapping file scopes during integration workflows.

What is the best way to standardize ForgePlan node design across development teams?▼

The best way to standardize ForgePlan node design is applying a 14-field node-spec schema. This enforces consistent governance, shared-model alignment, and acceptance criteria testing across development, testing, and integration workflows.

Why does node specification validation fail when shared_dependencies are not in the manifest?▼

Node specification validation fails because shared_dependencies must reference manifest-defined shared models. If an entity used by multiple nodes is not declared in the manifest, the $shared reference breaks governance rules.

Related Skills

Explore More Software Engineering Skills→
TonyQ-AITonyQ-AI
9

domain-modeling

Extract core business concepts, entity relationships, and domain rules from requirement specifications.

Community
Intermediate
Yukine5377Yukine5377

ba-n8n-node-config

Identify operation-aware field requirements and validate n8n node configurations.

Community
Advanced
cybersadercybersader
5

json-canvas

Create and edit JSON Canvas files with nodes, edges, and groups.

Community
Advanced
furqan90furqan90

spec-remix

Reuse validated Project Spec files to generate v1.1-conformant updated specs.

Community
Intermediate