spec-foundation

Create product, architecture, environment, and process specification artifacts for new software projects.

1|Updated Jun 29, 2026
One-click install
npx skills add https://github.com/mckissinger/keel --skill spec-foundation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-foundation
Source: https://github.com/mckissinger/keel/tree/main/skills/spec-foundation
Command: npx skills add https://github.com/mckissinger/keel --skill spec-foundation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents autonomous software projects from starting with fragile assumptions by creating a durable foundation of product, architecture, environment, and process specifications.

Core Features & Use Cases

  • Foundation Specification: Creates product, architecture, data model, environment contract, decisions, and deferrals artifacts that guide future development.
  • Project Governance Setup: Establishes CLAUDE.md guidance, verification workflows, GitHub processes, and milestone rules for reliable autonomous builds.
  • Use Case: A team starting a new application can use this Skill after defining the app skeleton to create the shared specifications and operational rules needed before feature implementation begins.

Quick Start

Use the spec-foundation skill to create the foundational specs and project guidance files for my new software project.

Frequently Asked Questions about spec-foundation

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

FAQPage Schema
How do I set up project specifications before starting autonomous software development?

Project specifications are established by creating durable foundational artifacts for product backlogs, architecture planning, and environment contracts before coding begins. This prevents autonomous software projects from starting with fragile assumptions.

What governance artifacts do I need for reliable autonomous development workflows?

Reliable autonomous development workflows require governance artifacts like CLAUDE.md guidance, verification processes, GitHub workflow rules, and milestone definitions to ensure structured and reliable feature delivery.

When should I create architecture and data model specifications for a greenfield application?

Architecture and data model specifications should be created immediately after defining the application skeleton during a greenfield kickoff, establishing the shared operational rules needed before any feature implementation begins.

Can I use this specification setup for an existing software project?

This specification setup is designed for greenfield application kickoffs requiring foundational product, architecture, and environment contracts. It is not intended for existing projects that already have established specifications.

What is the best way to prevent fragile assumptions in autonomous coding projects?

Preventing fragile assumptions requires building a durable foundation of stack-aware specifications and deferral artifacts that guide future development, ensuring autonomous coding agents follow structured project conventions.

Do I need structured specification files to support reliable feature delivery?

Structured specification files are required to support reliable feature delivery, providing the necessary environment contracts, product backlogs, and verification workflows that govern autonomous development tasks.