alejandro-cedeno-10/agentic-sdd-kit

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.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/alejandro-cedeno-10/agentic-sdd-kit --skill sdd-checklist

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

Requirements quality checklist

--strict validation proves a spec is well-FORMED; it doesn't prove it's well-SPECIFIED. This skill generates a tailored checklist and grades the change against it, so gaps in clarity or coverage surface before code — not in review.

When to use

  • At the sdd-feature-flow human approval gate, to decide whether to approve the spec.
  • Before /opsx:apply or launching implementation on any non-trivial change.

Procedure

  1. Read the change: openspec/changes/<id>/proposal.md, design.md, tasks.md, and the

delta spec(s); plus openspec/project.md (the constitution) if present.

  1. Generate the checklist, tailored to what this change touches. Cover at least:
  • Completeness — is every stated requirement addressed by the design AND the tasks?

Are error/empty/edge cases specified, not just the happy path? Are non-goals explicit?

  • Clarity — is each requirement testable and unambiguous (SHALL/MUST, concrete values)?

Any "should probably / TBD / etc." that hides a real decision?

  • Consistency — do proposal, design, tasks and delta agree? Any contradiction in scope,

data model, or naming? Does anything violate the constitution?

  • Testability — does each requirement have a scenario or a task that would fail if the

requirement were unmet? Is the verification path concrete?

  • Assumptions — is every load-bearing assumption either confirmed or flagged as an open

question (NOT silently baked in)?

  1. Grade each item pass / fail / n-a with a one-line reason, and list the fails first.
  2. Recommend: approve as-is, approve with the listed fixes, or send back for revision.

Output

A compact table (item · verdict · reason), fails first, then a one-line recommendation. Read-only — this skill changes no files; it produces the checklist and the verdict.

관련 작업

같은 저장소의 Skills

더 많은 Skills

모든 Skills
alejandro-cedeno-10
커뮤니티

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

1시간 설치 수
2
GitHub Stars
0
업데이트
7월 7일
alejandro-cedeno-10
커뮤니티

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

1시간 설치 수
2
GitHub Stars
0
업데이트
7월 7일
alejandro-cedeno-10
커뮤니티

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

1시간 설치 수
2
GitHub Stars
0
업데이트
7월 7일