메뉴
Shared foundation for the sdlc-* skill library: the engineering standard every session must meet, and the .ai-sdlc/state.md / journal.md file spec for cross-session handoff. Load when any sdlc-* skill references it or when reading/writing those files.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
End-of-work discipline for project repos: hostile validation of the diff before declaring work done, and handoff (settle the tree, update state.md, append the journal) before ending a session with changes. Triggered by the claim, not the diff — use before any done/ship verdict, even for small edits.
Start-of-work discipline for project repos: orientation before the first substantive task of a session, and planning whenever a task is multi-step, risky, ambiguous, or touches config that propagates beyond this machine. Execution is governed by sdlc-core.
| name | sdlc-core |
| description | Shared foundation for the sdlc-* skill library: the engineering standard every session must meet, and the .ai-sdlc/state.md / journal.md file spec for cross-session handoff. Load when any sdlc-* skill references it or when reading/writing those files. |
Foundation for the sdlc lifecycle skills (sdlc-start, sdlc-finish). It
holds the two things they share, so neither skill restates them:
references/STANDARD.md — the engineering standard: what "done well" means
for any change, regardless of which model executes it. Read it once per
session before doing substantive work under any sdlc-* skill; it is short
by design.references/STATE-SPEC.md — the format of a project's .ai-sdlc/state.md
and .ai-sdlc/journal.md, the handoff medium between sessions. Read it
before reading or writing either file.Portability: sibling skills reference these files as
~/.agents/skills/sdlc-core/.... When the library is installed elsewhere,
resolve them from the skills root instead — sdlc-core/ is always a sibling
directory of the invoking skill.
Precedence: repo-local instructions (AGENTS.md, CLAUDE.md) and explicit user instructions override this standard where they conflict. The standard fills gaps; it does not fight the repo.