Engineering and Git Discipline
The core package joins repository context with verification, rollback and delivery rules, then gives agents named workflows for review and Git operations.
- Verification gates
- Rollback safety
- Review and Git workflows
Open source · Engineering packages
Intelligence Dev Packs
Install reusable engineering workflows through the Intelligence CLI. Core adds verification and Git delivery; Spec adds the requirements-to-delivery lifecycle. Repository-owned rules keep final precedence.
Practice, Packaged
Reusable engineering discipline stays portable while repository-specific rules retain final precedence.
- Core
- The universal package carries verification gates, rollback safety, context discipline and the Git workflow from change through merge.
- Spec
- The optional package adds requirements, planning, validation, execution and documentation upkeep for spec-driven work.
- Precedence
- Package sources load before project sources, so a repository-owned artifact with the same name deliberately wins.
- Pinning
- Package intent stays in
intelligence.yaml. The exact source, tag and revision stay in the committedintelligence.lock.
What the Packages Carry
Requirements Through Delivery
The spec package turns a requirement into an approved plan, validates it against the repository, executes it and keeps the written record aligned.
- Requirements and plans
- Adversarial validation
- Execution and docs upkeep
Inspectable Before Install
Rules, agent definitions, skill instructions and changelogs remain plain files in the repository. Teams can review the operating layer before adding it.
- Plain-text artifacts
- Semantic version tags
- Public change history