Reference Documentation
Complete technical reference for the core SpecFact CLI platform.
This section documents the stable runtime, command topology, contracts, registry model, and ownership boundaries that specfact-cli owns directly.
For bundle-specific deep command guides and runbooks, use the canonical modules docs site at https://modules.specfact.io/.
Core Reference Topics
- Documentation URL contract - How core and modules sites relate; rules for cross-site links
- Commands - Exact grouped command topology and migration mapping
- Command Syntax Policy - Source-of-truth argument syntax conventions for docs
- Architecture - Technical design, module structure, and internals
- Authentication - Device code auth flows and token storage
- Debug Logging - Where and what is logged when using
--debug - Operational Modes - CI/CD vs CoPilot modes
- Module Categories - Category grouping model and canonical bundle assignments
- Module Contracts - Runtime-facing interfaces and ownership boundary
- Module Security - Marketplace/module integrity and publisher metadata
- Bridge Registry - Registry-facing bridge converter declarations
- Directory Structure - Project structure and organization
- Feature Keys - Key normalization and formats
- Dependency Resolution - Module/pip dependency resolution behavior
- Thorough Codebase Validation - Validation strategy overview
Live Command Topology Summary
Current top-level commands in the shipped CLI:
specfact initspecfact modulespecfact upgradespecfact project ...specfact backlog ...specfact code ...specfact spec ...specfact govern ...
Selected current command examples:
specfact code import from-bridge --adapter speckit --repo .specfact code import <bundle-name> --repo .specfact project snapshot --bundle <bundle-name>specfact project devops-flow --stage <plan|develop|review|release|monitor>specfact project sync bridge --adapter <adapter> --bundle <bundle-name>specfact project import <markdown-file> --bundle <bundle-name>specfact spec validate --bundle <bundle-name>specfact spec generate-tests --bundle <bundle-name> --output tests/specfact spec mock --bundle <bundle-name>specfact govern enforce sdd [BUNDLE]specfact code reprospecfact init ide --ide <cursor|vscode|copilot|...>specfact module install <name|namespace/name> [--scope user|project] [--source auto|bundled|marketplace] [--repo PATH]specfact module list [--source ...] [--show-origin] [--show-bundled-available]specfact module show <name>specfact module search <query>specfact module uninstall <name|namespace/name>specfact module upgrade [<name>|--all]
Ownership Boundary
- Core docs site: command topology, runtime lifecycle, contracts, registry, trust, architecture
- Canonical modules docs site: in-depth bundle commands, workflow tutorials, adapters, official module operations
See also: