Summary
Sharpen SpecFact's first-contact surfaces so README, GitHub repo metadata, docs.specfact.io, and modules.specfact.io tell one clear product story with a fast path to first value.
Why
SpecFact is strongest when presented as the validation and alignment layer for software delivery, especially across AI-assisted coding, brownfield reverse engineering, backlog/spec/code drift, and future policy enforcement. Current entry points still ask new users to absorb topology before they understand the product.
Scope
- rewrite README hero and onboarding flow
- improve GitHub repo messaging and topics guidance
- update docs.specfact.io landing guidance
- define modules-site handoff expectations
- ensure all entry points answer: what is it, why does it exist, why use it, what do I get, how do I start
OpenSpec
Change folder: openspec/changes/docs-14-first-contact-story-and-onboarding/
Parent feature: #356
Summary
Sharpen SpecFact's first-contact surfaces so README, GitHub repo metadata, docs.specfact.io, and modules.specfact.io tell one clear product story with a fast path to first value.
Why
SpecFact is strongest when presented as the validation and alignment layer for software delivery, especially across AI-assisted coding, brownfield reverse engineering, backlog/spec/code drift, and future policy enforcement. Current entry points still ask new users to absorb topology before they understand the product.
Scope
OpenSpec
Change folder: openspec/changes/docs-14-first-contact-story-and-onboarding/
Parent feature: #356