alejandro-cedeno-10 · Agent Skills

4 skills with substantive source documentation and an official publisher or observed installation demand. Read each skill’s original documentation through its card.

alejandro-cedeno-10

Community

sdd-checklist

Generate a requirements-quality checklist for an OpenSpec change and run it against the proposal/design/tasks/delta — validating completeness, clarity, consistency, and testability BEFORE you approve the spec. Modeled on GitHub Spec-Kit's /checklist. Use when reviewing a spec at the human approval gate, or before launching implementation, to catch under-specified requirements early.

Installationen

2

GitHub Stars

0

Aktualisiert

7. Juli

MIT1 Dateien

Skill-Details ansehen →

alejandro-cedeno-10

Community

sdd-clarify

Front door of the SDD flow. When the user asks for a feature or bug fix ("implementa…", "agrega…", "arregla…", "add…", "build…", "fix…"), FIRST scan the request + codebase context for load-bearing ambiguity and ask a few targeted clarifying questions (selectable options, recommended first) BEFORE writing any spec or code — then hand a well-formed goal to /opsx:propose (small) or the sdd-feature-flow workflow (large). Skip the questions when the request is already unambiguous. Modeled on GitHub S

Installationen

2

GitHub Stars

0

Aktualisiert

7. Juli

MIT1 Dateien

Skill-Details ansehen →

alejandro-cedeno-10

Community

sdd-context-intake

Ingest raw context the user pastes or points at — a ticket, a design doc, meeting notes, a spec, a URL, referenced files/paths — and have an agent READ and UNDERSTAND all of it, then synthesize a well-formed feature brief (goal, scope, constraints, and load-bearing unknowns) that feeds sdd-clarify and the sdd-feature-flow harness. Use at the very start of a feature when you have source material instead of a one-line goal, or whenever the user says "here's the context" / "read this" / dumps a tic

Installationen

2

GitHub Stars

0

Aktualisiert

7. Juli

MIT1 Dateien

Skill-Details ansehen →

alejandro-cedeno-10

Community

sdd-verify

Surface-aware end-to-end verification of a change — determine whether it touches a FRONTEND surface (rendered UI) or an API/backend surface, then validate the right way. Frontend → chrome-devtools MCP (open the affected page, screenshot, confirm it renders, check console/network/accessibility). API → a Playwright request script that hits the affected endpoints and asserts status + response shape. Use after implementing a change, or in the harness Validate step, to confirm it actually works in th

Installationen

2

GitHub Stars

0

Aktualisiert

7. Juli

MIT1 Dateien

Skill-Details ansehen →