Constraint-First Specification Architecture — production-grade from line one
A pipeline that turns a raw idea into exhaustively specified, test-driven, production-quality code through progressive gates. Stack-agnostic. Built for Antigravity on Linux/WSL. Every line of code is production-grade from the moment it's written.
npx cfsa-antigravity initThis installs the .agent/ folder, docs/ structure, and agent config files into your project.
| Command | Description |
|---|---|
cfsa-antigravity init |
Install the pipeline into your project |
cfsa-antigravity status |
Check installation + unfilled placeholders |
cfsa-antigravity init --force |
Overwrite existing installation |
cfsa-antigravity init --dry-run |
Preview what would be installed |
cfsa-antigravity init --path ./dir |
Install into specific directory |
If you are using AI-powered editors like Cursor or Windsurf, adding the .agent/ folder to your .gitignore may prevent the IDE from indexing the workflows. This results in slash commands (like /plan, /debug) not appearing in the chat suggestion dropdown.
Recommended Solution:
To keep the .agent/ folder local (not tracked by Git) while maintaining AI functionality:
- Ensure
.agent/is NOT in your project's.gitignore. - Instead, add it to your local exclude file:
.git/info/exclude
/ideate
The pipeline tells you what to run next at every step. You never have to guess.
The kit evolves independently of your project. To pull improvements into an existing project:
/sync-kit
This performs a semantic merge — it applies new workflows, skills, and rules from the upstream kit while preserving your project-specific values (tech stack, validation commands, filled placeholders). It will never overwrite your project decisions.
- First sync does a full comparison; subsequent syncs are incremental (commit-scoped)
- Tracks sync state in
.agent/kit-sync.mdso it knows what changed since last update - Flags any structural migrations needed (e.g., ideation format changes)
| Document | Contents |
|---|---|
| Pipeline Guide | Full walkthrough — every command, every stage |
| Kit Architecture | How the kit's internals work |
- Constraints before decisions — map what's decided before presenting options
- Exhaustive iteration over shallow speed — no ambiguity moves forward
- Work shifted left — design decisions made in spec, not in code
- Progressive decision locking — each stage locks decisions for downstream
- TDD as the implementation contract — Red → Green → Refactor, every slice
See CONTRIBUTING.md for how to set up, make changes, and submit PRs.