All authors

Claude Skills by developzoneio
github.com/developzoneio18 skills0 installs17 views
- Sd Atomic Task FormatCanonical format for atomic implementation tasks in specwright. Used by `sd-spec-architect` when authoring `02-tasks.md` and by `sd-implementer` when reading task contracts. ---Votes: 0GitHub stars: 8
- Sd Bootstrap GuardPhase 0 bootstrap guard for specwright workflow commands. `/sd:feature`, `/sd:bug`, `/sd:rca`, `/sd:refactor`, `/sd:perf`, `/sd:port` and `/sd:adr` read this file at runtime as Phase 0 step 1. Commands cannot load skills via frontmatter, so this is a runtime read rather than a `skills:` entry. The file is the single owner of the Layer-2 reads and of every message they print. A command's `## Phase 0` must not restate them; contract-lint `CL009` blocks it. ---Votes: 0GitHub stars: 8
- Sd Evidence CitationCitation discipline for specwright agents. Every finding, claim, or observation must be anchored to evidence. This skill applies to `sd-code-explorer`, `sd-debugger`, and `sd-reviewer`. ---Votes: 0GitHub stars: 8
- Sd Hypothesis TreeStructured hypothesis enumeration and verification for specwright debugging workflows. Used by `sd-debugger` in both bug investigation and perf hotspot analysis. ---Votes: 0GitHub stars: 8
- Sd Model EscalationModel escalation policy for specwright workflows: when the main thread invokes a subagent one model tier above its frontmatter default. This file is the single owner of the ladder, the invariants, the trigger table, the precedence rules, the logging contract and the rule IDs. Commands read it at runtime (they cannot load skills via frontmatter) and state only a rule ID and its trigger inputs - never the policy itself. `sd-spec-architect`, `sd-implementer` and `sd-debugger` load it via `skills...Votes: 0GitHub stars: 8
- Sd Pattern DisciplinePattern discovery and adherence rules for specwright. New code must read as if written by the team that wrote the surrounding code. Applied by `sd-spec-architect` (authoring `Pattern refs`), `sd-implementer` (following them), and `sd-reviewer` (verifying conformance). Read the section matching your role. The core rule applies to everyone. ---Votes: 0GitHub stars: 8
- Sd Port FidelityCross-project port fidelity policy for specwright. A port reproduces a donor implementation inside a host repo; the donor's form is the specification, and every departure from it is a citable decision rather than a preference. Authored into port specs by `sd-spec-architect` and enforced against the changeset by `sd-reviewer`. Read the section matching your role. The core rule and the deviation allowlist apply to everyone. ---Votes: 0GitHub stars: 8
- Sd Replan LoopSanctioned mid-execution re-plan protocol for specwright. Lets a workflow adapt when execution (or the batch review) reveals that `02-tasks.md` is wrong, **without** violating spec immutability or skipping a gate. Referenced at runtime by `/sd:feature` and `/sd:refactor` - the only two workflows that produce a `01-plan.md` + `02-tasks.md` pair to re-plan. Not used by `/sd:bug`, `/sd:perf`, or `/sd:rca`: bug and rca produce no atomic task list, and perf already carries its own adaptive loop (P...Votes: 0GitHub stars: 8
- Sd Retro LessonsLesson-extraction discipline for specwright. Turns retro prose into privacy-safe, reusable one-line rules that transfer to a codebase the author has never seen. This skill is the authority on the tag enum, the lesson record shape, and the abstraction rules. `scripts/validate-lessons.ps1` / `.sh` enforce the mechanical half; everything the validator cannot see is your job. ---Votes: 0GitHub stars: 8
- Sd Severity TaxonomySeverity taxonomy for specwright review findings. Apply this taxonomy in every review. Every finding must carry exactly one severity marker. Severities are NOT interchangeable. ---Votes: 0GitHub stars: 8
- Sd Spec TemplatesPer-template authoring rules for specwright. Used by `sd-spec-architect` when `TASK = create`. Each template has a dedicated section below. Read only the section matching the spec type being authored. ---Votes: 0GitHub stars: 8
- Sd Demo RuleDemo rule pack used by the contract-lint fixtures. Loaded by `sd-keeper`.Votes: 0GitHub stars: 8
- Sd Orphan RuleA rule pack nobody loads.Votes: 0GitHub stars: 8
- Sd Model EscalationDemo escalation policy used by the contract-lint fixtures. It owns the ladder and the trigger table; the demo workflow names only a rule ID.Votes: 0GitHub stars: 8
- Sd Model EscalationDemo escalation policy used by the contract-lint fixtures. It owns the ladder and the trigger table; the demo workflow names only a rule ID.Votes: 0GitHub stars: 8
- Sd Model EscalationDemo escalation policy used by the contract-lint fixtures. It owns the ladder and the trigger table; the demo workflow names only a rule ID.Votes: 0GitHub stars: 8
- Sd Model EscalationDemo escalation policy used by the contract-lint fixtures. It owns the ladder and the trigger table; the demo workflow names only a rule ID.Votes: 0GitHub stars: 8
- Sd Demo GuardDemo bootstrap guard read at runtime by the alpha command. It owns the messages below; a skill is never scanned by CL009, even under its own Phase 0 heading.Votes: 0GitHub stars: 8