Repository navigation
- - #22
Merged
Merged
-#22
Conversation
Start a draft PR for a skill that turns a one-line description into a spec draft, saved locally as markdown unless an artifact is asked. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Capture the plan-draft flow from the partner cafe session so a one-line description becomes a decision-ready spec draft. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Only the master template uses a table, so other md sections follow the no-table rule. Also collapse spec paths to dirs for the path check. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Master asked to keep marker definitions with the spec draft skill. spec-bdd now points to the new location. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Rename sdd-draft and keep each fact once so answered decisions do not drift from a top summary. Spec rules move out of CLAUDE.md with it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Small tasks get the spec as one chat reply instead of a document, using the same format as spec-draft. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Keep the answer quote in one place so inline markers cannot drift. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Master confirmed the sdd prefix for the draft and quick skills. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
비개발자도 읽는 기획 문서 스킬을 만들기 위한 빈 커밋 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
개발 요소 없이 기획만 담아 모든 직원이 읽고 의견을 내게 하기 위함 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
하위 에이전트가 공유 문서 링크를 못 열어 점검이 빠지는 것을 막기 위함 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
스킬 규칙의 근거가 된 결정을 PR에 남기기 위함 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…kill sdd-brief 스킬 추가
요구사항 문서 다음 단계인 설계 문서 스킬을 만들기 위한 빈 커밋 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
요구사항 문서 다음 단계로 설계 문서를 쓰게 하기 위해 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
requirements.md 와 design.md 를 한 폴더에 짝짓기 위해 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
작은 작업은 요구사항과 설계를 한 답으로 받기 위해 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
스킬의 결정 근거를 남기기 위해 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…skill sdd-design 스킬 추가
공용 포맷 문서 경로를 한 자리로 모으고 sdd: 이름으로 묶기 위해 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
공용 포맷 문서를 sdd-draft 하위가 아닌 묶음 공용 자리에 두기 위해 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
/sdd:quick 처럼 묶음 이름으로 부르기 위해 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
0.3.1 로 올려 /plugin update 로 새 구조를 받게 함. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
brief 는 #23 의 brief-format.md 구조를 따르고, 이 브랜치의 references/brief.md 는 지움. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ge-references sdd 단계별 템플릿·규칙을 레퍼런스 문서로 분리
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
스펙·설계·시나리오가 어긋나지 않고 워크트리를 지워도 남게 하려고
requirements.md 와 「완성」 design.md 를 입력으로 받아
~/.sdd/{리포}/{시각}_{요청}/features/ 에 저장한다.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…w-output sdd 작업 흐름·산출물 문서 추가와 bdd 저장 위치 변경
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
sdd:setup 이 humanize-korean@im-not-ai 를 설치하고, 마크다운 산출물은 spec-format 「윤문」을 거친다. 마커·ID·숫자·표·코드가 바뀌면 원본을 둔다. 스킬 추가가 아닌 동작 변경이라 0.5.0 으로 둘째 자리를 올렸다. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…e-korean sdd 산출물을 humanize-korean 으로 윤문
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
claude plugin eval 케이스 7개(스킬별)로 스펙 포맷 규칙을 regex·llm 으로 채점하고, run.ts 가 버전 자리에 따라 기준 결과 비교 또는 두 버전 재실행 + skill-creator 블라인드 비교를 고른다. compare.ts 가 회귀를 판정한다. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
작업 시작용 빈 커밋. 실제 변경은 후속 커밋에서 들어간다.
haiku 를 계정에서 비활성화해 두어 윤문 에이전트를 sonnet, effort low 로 부르게 한다. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…-sonnet-low fix(sdd): 윤문을 sonnet low로 돌리기
sdd 스킬 산출물 평가와 버전 회귀 판정 추가
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…-review sdd 참여자별 시나리오 검토 스킬 추가
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
요구사항 A~H, 설계 S~Z. 모자라면 기능을 나누자고 권한다. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
요구사항과 설계에 같은 식별자가 두 번 적혀 어긋나지 않게 한다. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
비개발자 문서에서 출처 괄호를 지우고 첫 문단 설명은 남긴다. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ft-planning-layer sdd 기획 초안에서 개발 수준 내용을 설계 문서로 옮기기
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.