alejandro-cedeno-10/agentic-sdd-kit

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…

소스 보기

사용 방법

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

시작 전 확인

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

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

Context intake for Spec-Driven Development

The user rarely starts with a clean one-line goal — they have a ticket, a doc, a thread, some files. This skill turns that raw material into the structured brief the SDD flow needs, WITHOUT guessing past what the sources actually say.

When to use

  • The user pastes a ticket / requirements / design doc / notes and says "do this".
  • The user names files, paths, or URLs as the source of truth.
  • Before sdd-clarify and before launching sdd-feature-flow, when the goal is buried in

material rather than stated.

Procedure

  1. Collect every source the user gave, verbatim: pasted text, plus anything referenced —

Read the named files, WebFetch the URLs, pull the ticket via its MCP/CLI if available. Do NOT stop at the pasted blurb if it points elsewhere.

  1. Delegate the reading when it's large or multi-source. Spawn a read-only agent (the

Explore or general-purpose agent) to ingest the sources and return a compact digest — this keeps the bulky material out of the main context. For a single short paste, read inline.

  1. Synthesize a brief with exactly these sections, grounded ONLY in the sources (mark

anything you inferred):

  • Goal — one or two lines: what to build and why (the "what/why", not the "how").
  • In scope / Out of scope — bullet lists drawn from the sources.
  • Constraints — data model, contracts, integrations, naming, limits the sources state.
  • Load-bearing unknowns — decisions the sources do NOT settle that would change code,

contract, or template structure. These become the questions for sdd-clarify.

  • Sources — the files/URLs/tickets you actually read.
  1. Hand off. Feed the unknowns to sdd-clarify (ask the user), then pass the resolved

brief as the goal (and any confirmed params) to the sdd-feature-flow workflow.

Rules

  • Ground everything in the sources. If the source doesn't say it, it's an unknown, not an

assumption — surface it, don't invent it. (This is the same discipline the harness's clarity gate enforces later; catching it here is cheaper.)

  • Never begin writing a spec or code from this skill — its only output is the brief.
  • Keep the digest tight; the point is to compress source material into decisions and unknowns.

관련 작업

같은 저장소의 Skills

더 많은 Skills

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

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.

1시간 설치 수
2
GitHub Stars
0
업데이트
7월 7일
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-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일