SpecFoundry

Opinionated workflow packs for OpenSpec.

SpecFoundry is an additive layer on top of OpenSpec. It packages reusable workflows, skills, command overlays, and project-knowledge conventions so teams can bring a deterministic, opinionated implementation style to any repository without forking OpenSpec itself.

The design goal is similar to shadcn/ui on top of a headless primitive system:

• OpenSpec remains the underlying framework and source of truth for spec-driven changes.
• SpecFoundry provides curated workflow packs, orchestration lanes, and local-copy installation.
• Each consuming repository provisions its own domain, priorities, and wiki sources locally.

Principles

• Add to OpenSpec, do not replace it.
• Keep the upstream relationship explicit.
• Prefer local-copy installation over opaque runtime magic.
• Keep the published repo domain-neutral.
• Push repo-specific priors and domain knowledge into consumer repos.
• Treat project knowledge as a maintained wiki, not disposable chat context.

Planned Packs

• core: opinionated change workflows on top of OpenSpec
• wiki: Karpathy-style maintained project knowledge conventions
• orchestration: supervisor and autopilot lanes for agent-led execution

Repository Layout

• packages/cli: install and provisioning CLI
• packs/: reusable workflow packs copied into consumer repositories
• docs/: architecture, packaging, and authoring guidance
• examples/: small consumer-repo examples

Status

This repository is being bootstrapped. The first milestone is:

1. define the pack model
2. build a local-copy installer
3. extract generic workflows from the originating repository
4. separate portable workflow logic from repo-local domain priors

Relationship To OpenSpec

SpecFoundry depends on OpenSpec being present in the target repository. It should:

• install additive commands and skills under its own namespace by default
• optionally offer compatibility overlays for selected /opsx:* commands
• preserve upstream OpenSpec workflows unless the user explicitly opts into overrides

Knowledge Model

SpecFoundry treats project knowledge as a maintained markdown wiki following the pattern described by Andrej Karpathy in llm-wiki.md:

• raw sources remain immutable
• the wiki is maintained and synthesized over time
• repo-level schema and conventions teach the agent how to keep the wiki healthy

This lets implementation workflows build on accumulated project knowledge rather than rediscovering context from scratch every session.