Right-size, ground, and gate SDLC decisions with SNC-sized depth, said-vs-assumed write-back, an evidence ledger, honest option cards, recorded approval, and self-review. Use when running brainstorm-feature, plan-feature, design-solution, or system-design-session.
80%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./.agents/skills/common/common-decision-discipline/SKILL.mdTrustworthy decisions are sized to the work, grounded in evidence, and approved on the record.
| SNC tier | Depth | Artifact |
|---|---|---|
tier=low (0-2) | Quick | Contract in chat, no file; approval in the Handoff Payload |
tier=medium (3-4) | Standard | Core brief file |
tier=high (5-6) | Deep | Full brief; decompose multi-subsystem ideas first; optional specialist-architecture-guard review |
common-task-complexity-routing; label as inference until scouted.tier=medium regardless of arithmetic SNC total; non-zero novelty or spread (S≥1 or N≥1 with C=2) escalates to tier=high.dev-fix; never compare fixes for an undiagnosed bug.assumed, and never re-present a shifted value as supplied.confirmed(<path>), assumed, or unknown; a search miss or empty local checkout is never absent capability, so search authorized refs/worktrees before concluding a capability missing or creating duplicate solutions.references/evidence-ledger.md.confirmed on the summary's authority.NOT RUN/not assessed is never PASS, and finite checks prove a response contract, not semantic safety, live behavior, or human acceptance.operator_profile=business, every question is answerable by "go with your suggestion".references/option-card.md).approval: pending | approved(<who>, <YYYY-MM-DD>) | assumed-autonomous. Review card ≤250 words (references/brainstorm-review.md); surface over-cap risk explicitly. Interactive: end with "Reply ok or corrections" (approves presented artifact only). Autonomous/channel mode: assumed-autonomous; tier=high still blocks on explicit human sign-off.repository_status and activation_status separately; use not_required when activation is outside the contract, and do not require an external VM/runtime artifact for approved repository-only publication unless the contract requires it.rule) or by using a default not covered by a rule (default-pending-review). Following an outcome explicitly selected by a human or using a routine tool is not a decision. Record only a permitted choice; the record never authorizes action or replaces a required human gate. See Decision Record for the rubric and examples.Stop when thinking: "too simple to need a brief", "they said implement, so skip intake", "list three options to look thorough", "approval to publish means deploy", "the summary already says confirmed", "the checks passed, so it is safe", "invent why to sound helpful". Each is a rationalization, not a reason.
approval is incomplete; settled facts are carried forward, not re-asked, and changed scope reopens affected decisions only.HoangNguyen0403/agent-skills-standard
11c8bd1
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.