capstone 플러그인

GentBajko/capstone스타 5개Apache-2.0작성자: Gent Bajko

Architecture reference generator: a docs/capstone/ index plus chapters stamped to commits, kept current by generate/sync, with doctor/review commands, a greenfield pipeline with a frontend-design stage, and a doc-grounded feature chain.

architecture documentation design-docs codebase-map architecture-docs skills

capstone 플러그인 설치 방법

두 명령을 모두 Claude Code 안에서 실행하십시오. 첫 번째는 마켓플레이스를 한 번 추가하고, 두 번째는 플러그인을 설치합니다.

Claude Code

/plugin marketplace add GentBajko/capstone
/plugin install capstone@capstone-marketplace

capstone 구성 요소

플러그인 파일에서 읽어온 12개의 항목입니다.

Skills 10

작업이 일치하면 Claude가 로드합니다

core
Internal to the capstone suite - carries the shared rules (references/) and scripts every capstone subcommand reads; it exists so npx-skills installs ship them alongside the command skills. Not meant to be invoked directly; when invoked anyway, run references/../scripts/help.sh and output its stdout verbatim.
doctor
Use when the capstone docs area needs a consistency check or repair - torn writes, done markers without ledger entries, voided plan approvals, index rows pointing at missing files, absorption gaps - reports findings with their owning rules, then applies only the repairs the user approves.
feature
Use when the user wants one feature taken from idea to working code - "add a feature", "build X end to end", "take X from idea to shipped" - runs the feature chain groom → plan → implement consecutively, detecting the feature's stage and resuming at the first incomplete one. For the whole-product greenfield pipeline use start; to execute an already-approved plan use implement. Always asks subagents or inline before each new or resumed run.
groom
Use when starting work on a feature or change for a project that already has capstone docs - "new feature", "add a feature", "implement X", "build X", "design a feature", "spec it out", "flesh out", "refine this idea", "let's work on X" - a doc-grounded one-question-at-a-time interview producing a traceable feature spec in docs/capstone/features/, the first stage of the feature chain before plan and implement. Not whole-product discovery (mockup), not the greenfield pipeline (start); to carry one feature from idea to working code in a single run use feature.
help
Use when asked what the capstone plugin can do - prints the usage block.
implement
Use when an approved feature plan is ready to become code - executes plan.md task by task with verification, in subagents or inline as you pick, reviews the diff recursively until no new findings survive, then refreshes the affected reference chapters.
map
Use when asked to build, refresh, update, or check a codebase's architecture reference docs - "map the codebase", "document this repo", "are the docs current", "bring the docs in line with the code" - writes a docs/capstone/ index plus topic chapters, the logic/ business-logic map and the uiux/ surface map, then on later runs rewrites only the files whose covered paths drifted. One verb for both - no reference yet means build it, an existing one means refresh it. "map check" is the read-only trust report that writes nothing; "map rebuild" forces a full rewrite; a topic name targets one chapter.
plan
Use when a groomed feature spec needs an implementation plan - studies the chapters the spec cites, writes a task-by-task TDD plan an engineer with zero context could execute, gated on user approval.
review
Use when asked for an opinionated review of the codebase - architecture/backend findings, UI findings against the project's own design docs, or both - severity-ranked with evidence, written to docs/capstone/review.md. Bare "review" does both sides; "review backend" or "review frontend" does one. "review retro [session]" is the third judgment axis - it reads a finished session and proposes edits to standards.md and the project's AGENTS.md/CLAUDE.md instead of judging code. Opt-in judgment; never edits code.
start
Use when the user says just "capstone" with nothing else, or asks to start or continue the capstone pipeline - runs the greenfield chain one stage at a time, detecting completed stages and resuming at the first incomplete one. A stage word as the argument (mockup, logic, uiux, architecture, standards, stack, build) enters that one stage directly; "start stack refresh" re-vets recorded picks. The session review is not here - that is "review retro". Always asks subagents or inline before each new or resumed run.

Hooks 2

다음 이벤트에서 실행됩니다

SessionStartcommand
파일에 설명이 없습니다.
UserPromptExpansioncommand
capstone:help

Claude Code에서 capstone 사용하기

Skills는 명령어가 필요하지 않습니다. 요청이 설명과 일치하면 Claude가 이를 읽습니다.

업데이트, 비활성화 또는 삭제

플러그인 업데이트 (shell): claude plugin update capstone@capstone-marketplace
marketplace 새로고침: /plugin marketplace update capstone-marketplace
일시적으로 비활성화: /plugin disable capstone@capstone-marketplace
삭제: /plugin uninstall capstone@capstone-marketplace

capstone의 스킬

coreGentBajko/capstone
Internal to the capstone suite - carries the shared rules (references/) and scripts every capstone subcommand reads; it exists so npx-skills installs ship them alongside the command skills. Not meant to be invoked directly; when invoked anyway, run references/../scripts/help.sh and output its stdout verbatim.
35개 파일
5스타
doctorGentBajko/capstone
Use when the capstone docs area needs a consistency check or repair - torn writes, done markers without ledger entries, voided plan approvals, index rows pointing at missing files, absorption gaps - reports findings with their owning rules, then applies only the repairs the user approves.
5스타
featureGentBajko/capstone
Use when the user wants one feature taken from idea to working code - "add a feature", "build X end to end", "take X from idea to shipped" - runs the feature chain groom → plan → implement consecutively, detecting the feature's stage and resuming at the first incomplete one. For the whole-product greenfield pipeline use start; to execute an already-approved plan use implement. Always asks subagents or inline before each new or resumed run.
5스타
groomGentBajko/capstone
Use when starting work on a feature or change for a project that already has capstone docs - "new feature", "add a feature", "implement X", "build X", "design a feature", "spec it out", "flesh out", "refine this idea", "let's work on X" - a doc-grounded one-question-at-a-time interview producing a traceable feature spec in docs/capstone/features/, the first stage of the feature chain before plan and implement. Not whole-product discovery (mockup), not the greenfield pipeline (start); to carry one feature from idea to working code in a single run use feature.
5스타
helpGentBajko/capstone
Use when asked what the capstone plugin can do - prints the usage block.
5스타
implementGentBajko/capstone
Use when an approved feature plan is ready to become code - executes plan.md task by task with verification, in subagents or inline as you pick, reviews the diff recursively until no new findings survive, then refreshes the affected reference chapters.
5스타
mapGentBajko/capstone
Use when asked to build, refresh, update, or check a codebase's architecture reference docs - "map the codebase", "document this repo", "are the docs current", "bring the docs in line with the code" - writes a docs/capstone/ index plus topic chapters, the logic/ business-logic map and the uiux/ surface map, then on later runs rewrites only the files whose covered paths drifted. One verb for both - no reference yet means build it, an existing one means refresh it. "map check" is the read-only trust report that writes nothing; "map rebuild" forces a full rewrite; a topic name targets one chapter.
5스타
planGentBajko/capstone
Use when a groomed feature spec needs an implementation plan - studies the chapters the spec cites, writes a task-by-task TDD plan an engineer with zero context could execute, gated on user approval.
5스타
reviewGentBajko/capstone
Use when asked for an opinionated review of the codebase - architecture/backend findings, UI findings against the project's own design docs, or both - severity-ranked with evidence, written to docs/capstone/review.md. Bare "review" does both sides; "review backend" or "review frontend" does one. "review retro [session]" is the third judgment axis - it reads a finished session and proposes edits to standards.md and the project's AGENTS.md/CLAUDE.md instead of judging code. Opt-in judgment; never edits code.
5스타
startGentBajko/capstone
Use when the user says just "capstone" with nothing else, or asks to start or continue the capstone pipeline - runs the greenfield chain one stage at a time, detecting completed stages and resuming at the first incomplete one. A stage word as the argument (mockup, logic, uiux, architecture, standards, stack, build) enters that one stage directly; "start stack refresh" re-vets recorded picks. The session review is not here - that is "review retro". Always asks subagents or inline before each new or resumed run.
5스타

capstone 플러그인 질문

capstone 플러그인은 어떻게 설치하나요?

Claude Code에서 /plugin marketplace add GentBajko/capstone를 실행한 다음 /plugin install capstone@capstone-marketplace을 실행하십시오.

capstone 플러그인에는 무엇이 포함되나요?

capstone은(는) 10개 스킬, 훅을(를) 묶습니다.

capstone 플러그인을 어떻게 업데이트하거나 삭제하나요?

shell에서 claude plugin update capstone@capstone-marketplace를 사용하여 업데이트하거나 /plugin의 Installed 탭에서 수행하세요. 삭제하려면 /plugin uninstall capstone@capstone-marketplace을 사용하세요.

capstone 플러그인의 라이선스는 무엇인가요?

플러그인 manifest에 명시된 대로 Apache-2.0입니다.

capstone 플러그인

GentBajko/capstone스타 5개Apache-2.0작성자: Gent Bajko

capstone 구성 요소

플러그인 파일에서 읽어온 12개의 항목입니다.

Skills 10

작업이 일치하면 Claude가 로드합니다

core
Internal to the capstone suite - carries the shared rules (references/) and scripts every capstone subcommand reads; it exists so npx-skills installs ship them alongside the command skills. Not meant to be invoked directly; when invoked anyway, run references/../scripts/help.sh and output its stdout verbatim.
doctor
Use when the capstone docs area needs a consistency check or repair - torn writes, done markers without ledger entries, voided plan approvals, index rows pointing at missing files, absorption gaps - reports findings with their owning rules, then applies only the repairs the user approves.
feature
Use when the user wants one feature taken from idea to working code - "add a feature", "build X end to end", "take X from idea to shipped" - runs the feature chain groom → plan → implement consecutively, detecting the feature's stage and resuming at the first incomplete one. For the whole-product greenfield pipeline use start; to execute an already-approved plan use implement. Always asks subagents or inline before each new or resumed run.
groom
Use when starting work on a feature or change for a project that already has capstone docs - "new feature", "add a feature", "implement X", "build X", "design a feature", "spec it out", "flesh out", "refine this idea", "let's work on X" - a doc-grounded one-question-at-a-time interview producing a traceable feature spec in docs/capstone/features/, the first stage of the feature chain before plan and implement. Not whole-product discovery (mockup), not the greenfield pipeline (start); to carry one feature from idea to working code in a single run use feature.
help
Use when asked what the capstone plugin can do - prints the usage block.
implement
Use when an approved feature plan is ready to become code - executes plan.md task by task with verification, in subagents or inline as you pick, reviews the diff recursively until no new findings survive, then refreshes the affected reference chapters.
map
Use when asked to build, refresh, update, or check a codebase's architecture reference docs - "map the codebase", "document this repo", "are the docs current", "bring the docs in line with the code" - writes a docs/capstone/ index plus topic chapters, the logic/ business-logic map and the uiux/ surface map, then on later runs rewrites only the files whose covered paths drifted. One verb for both - no reference yet means build it, an existing one means refresh it. "map check" is the read-only trust report that writes nothing; "map rebuild" forces a full rewrite; a topic name targets one chapter.
plan
Use when a groomed feature spec needs an implementation plan - studies the chapters the spec cites, writes a task-by-task TDD plan an engineer with zero context could execute, gated on user approval.
review
Use when asked for an opinionated review of the codebase - architecture/backend findings, UI findings against the project's own design docs, or both - severity-ranked with evidence, written to docs/capstone/review.md. Bare "review" does both sides; "review backend" or "review frontend" does one. "review retro [session]" is the third judgment axis - it reads a finished session and proposes edits to standards.md and the project's AGENTS.md/CLAUDE.md instead of judging code. Opt-in judgment; never edits code.
start
Use when the user says just "capstone" with nothing else, or asks to start or continue the capstone pipeline - runs the greenfield chain one stage at a time, detecting completed stages and resuming at the first incomplete one. A stage word as the argument (mockup, logic, uiux, architecture, standards, stack, build) enters that one stage directly; "start stack refresh" re-vets recorded picks. The session review is not here - that is "review retro". Always asks subagents or inline before each new or resumed run.

Hooks 2

다음 이벤트에서 실행됩니다

SessionStartcommand
파일에 설명이 없습니다.
UserPromptExpansioncommand
capstone:help

capstone의 스킬

coreGentBajko/capstone

Internal to the capstone suite - carries the shared rules (references/) and scripts every capstone subcommand reads; it exists so npx-skills installs ship them alongside the command skills. Not meant to be invoked directly; when invoked anyway, run references/../scripts/help.sh and output its stdout verbatim.

35개 파일

5스타

doctorGentBajko/capstone

Use when the capstone docs area needs a consistency check or repair - torn writes, done markers without ledger entries, voided plan approvals, index rows pointing at missing files, absorption gaps - reports findings with their owning rules, then applies only the repairs the user approves.

5스타

featureGentBajko/capstone

Use when the user wants one feature taken from idea to working code - "add a feature", "build X end to end", "take X from idea to shipped" - runs the feature chain groom → plan → implement consecutively, detecting the feature's stage and resuming at the first incomplete one. For the whole-product greenfield pipeline use start; to execute an already-approved plan use implement. Always asks subagents or inline before each new or resumed run.

5스타

groomGentBajko/capstone

Use when starting work on a feature or change for a project that already has capstone docs - "new feature", "add a feature", "implement X", "build X", "design a feature", "spec it out", "flesh out", "refine this idea", "let's work on X" - a doc-grounded one-question-at-a-time interview producing a traceable feature spec in docs/capstone/features/, the first stage of the feature chain before plan and implement. Not whole-product discovery (mockup), not the greenfield pipeline (start); to carry one feature from idea to working code in a single run use feature.

5스타

helpGentBajko/capstone

Use when asked what the capstone plugin can do - prints the usage block.

5스타

implementGentBajko/capstone

Use when an approved feature plan is ready to become code - executes plan.md task by task with verification, in subagents or inline as you pick, reviews the diff recursively until no new findings survive, then refreshes the affected reference chapters.

5스타

mapGentBajko/capstone

Use when asked to build, refresh, update, or check a codebase's architecture reference docs - "map the codebase", "document this repo", "are the docs current", "bring the docs in line with the code" - writes a docs/capstone/ index plus topic chapters, the logic/ business-logic map and the uiux/ surface map, then on later runs rewrites only the files whose covered paths drifted. One verb for both - no reference yet means build it, an existing one means refresh it. "map check" is the read-only trust report that writes nothing; "map rebuild" forces a full rewrite; a topic name targets one chapter.

5스타

planGentBajko/capstone

Use when a groomed feature spec needs an implementation plan - studies the chapters the spec cites, writes a task-by-task TDD plan an engineer with zero context could execute, gated on user approval.

5스타

reviewGentBajko/capstone

Use when asked for an opinionated review of the codebase - architecture/backend findings, UI findings against the project's own design docs, or both - severity-ranked with evidence, written to docs/capstone/review.md. Bare "review" does both sides; "review backend" or "review frontend" does one. "review retro [session]" is the third judgment axis - it reads a finished session and proposes edits to standards.md and the project's AGENTS.md/CLAUDE.md instead of judging code. Opt-in judgment; never edits code.

5스타

startGentBajko/capstone

Use when the user says just "capstone" with nothing else, or asks to start or continue the capstone pipeline - runs the greenfield chain one stage at a time, detecting completed stages and resuming at the first incomplete one. A stage word as the argument (mockup, logic, uiux, architecture, standards, stack, build) enters that one stage directly; "start stack refresh" re-vets recorded picks. The session review is not here - that is "review retro". Always asks subagents or inline before each new or resumed run.

5스타