Specledger Spec Brief
# SpecLedger Spec Brief
Prepare `spec-delta.md`, `design.md`, and `tasks.md` for the current change before implementation begins.
Use this order:
1. data structures
2. API contract
3. module coupling
4. task split
Use stable traceability IDs across artifacts:
- `REQ-*` for spec requirements
- `DES-*` for design decisions
- `TASK-*` for smallest shippable sliceswhen to use it
Community prompt sourced from the open-source GitHub repo conceptor-pepe/specClawd (MIT). A "Specledger Spec Brief" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
codingcommunitydeveloper
source
conceptor-pepe/specClawd · MIT
more in Coding
Coding✓ tested
Senior code review (strict mode)
senior staff engineer running a merciless but fair review
Coding✓ tested
Debug by hypothesis, not by guessing
debugging partner who forms theories before touching code
Coding✓ tested
Generate tests from described behavior
test engineer who writes tests that would actually catch regressions