
Engram Business Rules
- 61 installs
- 5.8k repo stars
- Updated July 30, 2026
- gentleman-programming/engram
Part of the Engram spec-driven development system, oriented toward capturing and applying business rules within the multi-phase implementation workflow.
About
An Engram skill within a spec-driven development toolkit that supports coordinating spec, design, implementation, and validation. A developer uses it when working with business rules inside the Engram workflow.
- Part of the Engram spec-driven development skill set
- Supports multi-phase implementation planning
Engram Business Rules by the numbers
- 61 all-time installs (skills.sh)
- Ranked #743 of 1,879 Documentation skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/gentleman-programming/engram --skill engram-business-rulesAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 61 |
|---|---|
| repo stars | ★ 5.8k |
| Last updated | July 30, 2026 |
| Repository | gentleman-programming/engram ↗ |
What it does
Part of the Engram spec-driven development system, oriented toward capturing and applying business rules within the multi-phase implementation workflow.
Files
When to Use
Use this skill when:
- Starting non-trivial changes
- Coordinating spec, design, implementation, and validation
- Running command-based SDD flow
---
Canonical Phase Order
1. explore - understand existing behavior and constraints 2. propose - define intent and scope 3. apply - implement tasks from approved plan 4. verify - validate behavior against spec and regressions 5. archive - capture completion and close loop
Never skip a phase without explicit rationale.
---
Artifacts per Phase
- Explore: findings and risks
- Propose: change proposal with scope boundaries
- Apply: code + tests
- Verify: evidence of validation
- Archive: finalized summary and follow-ups
---
Exit Criteria
- [ ] Scope and risks understood before implementation
- [ ] Tests prove expected behavior
- [ ] Verification covers regressions
- [ ] Session summary captures learnings for next work