On-demand "what's new" generator. Main context (which knows the impending change) writes keepachangelog-style entries to a fragment file at `.claude/state/whatsnew/<slug>.json` (gitignored, transient). An optional per-project `project.json → whatsnew.route_workflow` names a routing workflow that consumes the fragment and renders it wherever the project wants (a site page, a release body, a docs page). Not a workflow phase — it never blocks a commit, and it never writes `CHANGELOG.md` (that file is owned solely by semantic-release in CI).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Emits a structured "what's new" fragment for a set of changes. The fragment is a gitignored handoff buffer; a per-project routing workflow turns it into whatever surface the project wants. The generator makes no assumption about the destination, and it never touches CHANGELOG.md — semantic-release owns that file at release time.
This skill is not a mandatory workflow phase. It is invoked on demand (and, when a project wires whatsnew.route_workflow, handed off to that routing workflow). Version is never stored in the fragment: the routing target reads the shipped version at publish time.
.claude/state/whatsnew/), each object shaped { "category": "<Added|Changed|Deprecated|Removed|Fixed|Security>", "title": "<short headline>", "body": "<one or two sentences>", "highlight": <bool, optional> }.--slug <slug> --entries-file <path> (optionally --project-root <root>). It validates the entries, writes the fragment to .claude/state/whatsnew/<slug>.json, and resolves the optional routing target.project.json → whatsnew.route_workflow names a workflow, that workflow is the documented consumer of the fragment; it reads the fragment and writes its own committed output. If the knob is absent or null, the generator still succeeds and the fragment simply sits at the conventional path unconsumed.whatsnew.mjs — the generator entrypoint. Reads the entries file, writes the fragment, reports the routing target.fragment-writer.mjs — validates entries and serializes the fragment { slug, generated_at, entries[{category, title, body, highlight?}] }. No version field.route-resolver.mjs — resolves project.json → whatsnew.route_workflow (string track id, or null by read-time default).classifier.mjs — defines the canonical keepachangelog category set that fragment-writer.mjs validates entries against.CHANGELOG.md. That file is owned by semantic-release in CI. The generator only ever writes the gitignored fragment..claude/state/whatsnew/<slug>.json is gitignored; a routing workflow that needs persistence commits its own rendered output, not the buffer.whatsnew.route_workflow unset.아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Phase 10.5 — move the slug's workflow artifacts (intake, scout, research, spec, approvals, swarm state, security reports, rendered diagrams) to docs/archive/<YYYY-MM-DD>/<slug>/. Runs before /commit so the committed tree is clean of work-in-flight files. workflow.json stays live and gets archived as the first step of /commit.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Drift check between the baseline implementation on disk and the claims in `docs/init/seed.md` + cross-references in CLAUDE.md, README.md, and the rendered docs site. Verifies hook/agent/skill/command names + counts, settings.json wiring, project.json key presence, .mcp.json servers, vendored license files, and helper script presence. Exit 0 PASS / 1 FAIL — suitable for CI. Read-only; safe to invoke any time.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
PM-mode brainstorm helper. Captures the requirement via Socratic dialogue before any entry phase (`/intake`, `/spec`, `/tdd`) drafts its artifact. Stage 0 skip-check, Stage 1 gap-analysis, Stage 2 probe-loop, Stage 3 confirm-and-persist. Output lives at `docs/brief/<slug>.md`. Never proposes solutions — Stage 2 dialogue discipline is structurally enforced via `discipline.mjs`.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Draft a Business Requirements Document (BRD) for cross-functional or stakeholder-heavy work that needs more structure than an intake. Use after `/intake` when the request spans multiple systems/teams, carries regulatory weight, or needs formal sign-off. Output lives at `docs/brd/<slug>.md`.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Workflow track for tasks that need no TDD — documentation edits, governance count bumps, vendored-skill content updates, configuration tweaks, formatting, typo fixes, dependency bumps where no project code changes. Skips `/scenario` and `/implement` (no failing test to drive) and runs the work directly. `archive`, `memory-sync`, `/grant-commit`, and `/commit` remain mandatory. `verify`, `simplify`, `integrate`, and `document` are conditional — required when the diff hits one of the listed triggers, optional otherwise. `verify` is skipped only when the diff is pure-docs/prose AND `project.json → test.kind` is `behavior` (absent/invalid `test.kind` → `structural` → verify runs). Chore is a stripped-down pipeline, not a bypass; never silently skip a conditional phase whose triggers apply.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze a codebase and recommend Claude Code automations (hooks, subagents, skills, plugins, MCP servers). Use when user asks for automation recommendations, wants to optimize their Claude Code setup, mentions improving Claude Code workflows, asks how to first set up Claude Code for a project, or wants to know what Claude Code features they should use.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.