All skills
logging-design-gate
ProfessionalRuntime top levelUse task-agent for bounded logging changes or review-agent to independently assess placement, schema, severity, redaction, correlation, and signal tradeoffs. Skip work with no logging impact and self-review requests.
- Group
- Quality, security, reliability and delivery gates
- Routing mode
- automatic
- Supported roles
- MainAnalysisTaskReview
- Source
- SKILL.md
Use when
Trigger signals that make this skill the right owner
- logging schema or redaction change
- diagnostic gap
Do not use when
Anti-triggers — as binding as the triggers above
- no logging impact
- self review request
Required inputs
What must be supplied before this skill can decide anything
- acceptance
- logging decision
Output contract
What this skill owes the next role
- logging changes
- logging verdict
- signal risk
Escalation signals
When this skill must hand the decision back
- scope, authority, or material risk exceeds the selected task contract
Related expertise
4 Layer 3 candidates may be loaded behind this skill. A single task loads at most three, and only when the current evidence justifies them.
Targeted references
Each reference carries its own load condition. None of them enter context by default.
| Reference | Load when | Do not load when | Required by |
|---|---|---|---|
| checklist.mddecision-checklist | A bounded L2 mode needs compact checks for its triggered purpose, placement, fields, redaction, level, signal split, or validation risk | The root contract is enough or targeted proof fields are required | TaskReview |
| index.mdindex | competing logging design gate references require dependency, conflict, or output-fragment selection | the logging design gate root or a task-named reference already resolves selection | TaskReview |
| logging-output-and-gates.mdtargeted | L3-L5 implementation or review needs mode-specific closure and targeted gates for selected purpose, placement, schema safety, correlation, volume, sink, or failure-visibility risk | The root result is sufficient and no selected risk needs the extended proof contract | TaskReview |
| logging-selection-criteria.mdtargeted | A concrete purpose, level, field, redaction, correlation, placement, or signal choice needs more detail than the root contract | The root contract determines the no-log or bounded logging decision | TaskReview |