Idea: SpecLang — make spec.md the source of truth, not a generator input

[Quratulain-bilal]

@mnriem — floating an idea before building.

Concept: A .spec file format that acts as durable source-of-truth.
Every git commit re-runs spec-kit pipeline → keeps implementation in sync
forever. No drift between spec and code.

Why it fits spec-kit:

• Same artifacts (spec.md/plan.md/tasks.md), new lifecycle
• Solves the Add John Lam as contributor and release badge #1 brownfield problem: spec-implementation drift
• Composable with existing extensions (sync, refine, validate)
• Optional, opt-in, doesn't change defaults

Asking before I build:

1. Does spec-as-source-of-truth align with project philosophy?
2. Better as extension or external tool?
3. Naming — SpecLang / SpecSync / something else?

[mnriem]

You can create a Spec Kit workflow to accomplish what you are looking for. Feel free to submit your workflow to yes ..... the community catalog.

[Quratulain-bilal]

Thanks @mnriem — that's exactly the right framing. I'll build it as
spec-kit-speclang (workflow extension) and submit to the community
catalog. Will reference this discussion in the PR. Targeting end of
this week for v1.0.0.