U Spec Back Writing
Checklist and quality rules for backend specification writing. Used by the Back Spec Agent to ensure completeness and correctness of .back.md artifacts.
Install
$ agentstack add skill-zig999-siegard-code-u-spec-back-writing ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-zig999-siegard-code-u-spec-back-writing) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Skill: Backend Spec Writing
Data Modeling Checklist
- [ ] All entities have explicit primary key strategy (uuid, auto-increment, composite)
- [ ] All FKs have explicit
on-deleterule (CASCADE, SET NULL, RESTRICT) - [ ] Index justification documented for all non-PK fields used in WHERE clauses
- [ ] Enum values listed explicitly — no open-ended "etc."
- [ ] Nullable vs. required fields declared for every column
- [ ] Soft-delete strategy declared if entities can be deactivated
- [ ] If soft-delete: corresponding endpoint uses PATCH or POST (never DELETE)
- [ ] If hard-delete: DELETE endpoint is justified in a BR (irreversible by design)
Business Rules Checklist
- [ ] Each BR references the UC that originates it (
UC-NN) - [ ] Validation layer specified for each BR (API gateway | service | repository)
- [ ] Error code registered in global catalog for each BR violation
- [ ] Edge cases documented for each BR (what happens at boundary values)
- [ ] Conflict resolution documented when two BRs can contradict each other
State Machine Checklist
- [ ] All states enumerated (no implicit "other" state)
- [ ] All valid transitions mapped (From → Trigger → To)
- [ ] Guard conditions explicit for each transition
- [ ] Terminal states identified
- [ ] Invalid transition behavior documented (reject silently or throw error)
Event Payload Checklist
- [ ] Producer domain identified
- [ ] Consumer domains listed
- [ ] Payload schema fields typed with JSON schema or TypeScript equivalent
- [ ] At-least-once or exactly-once delivery semantics declared
- [ ] Event versioning strategy declared (if events are persisted or shared cross-service)
Quality Gate
The Back Spec Agent must not mark a .back.md as ready for the Validator unless all checked items in each applicable section above are filled. Sections not applicable to the domain (e.g., no events) may be omitted with a note: N/A — no domain events.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: zig999
- Source: zig999/siegard-code
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.