메뉴
Create a new proposal (RFC) document. Use when proposing a change, new feature, or architectural decision that needs team review. Handles numbering, naming, and template population. Use --root for cross-cutting proposals that affect multiple modules.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Validate that a pull request follows principled conventions: references a plan or proposal, has correct labels, includes required sections in the description, and links to relevant documents. Use in CI or before merging to enforce PR quality.
Generate a structured pull request description from a DDD plan task. Reads the plan, task manifest, and implementation branch to produce a PR body with references to the originating proposal, plan, ADRs, and related tasks. Use when opening a PR for plan-driven work.
Process open GitHub issues through the principled pipeline. Lists untriaged issues, normalizes their metadata, ingests them into the documentation pipeline, and reports a summary. Operates as the batch entry point — delegates to /ingest-issue for each individual issue.
Implementation orchestration strategy for the Principled framework. Consult when working with DDD plan execution, git worktrees for task isolation, task manifests, or the decompose-spawn-validate-merge lifecycle. Covers worktree management, sub-agent patterns, task state machines, and manifest schema.
Top-level orchestrator for DDD plan execution. Decomposes a plan into tasks, iterates through phases respecting dependencies, spawns worktree-isolated agents, validates implementations, and merges results. Runs inline to coordinate multiple sub-agent spawns. Use for automated end-to-end plan execution.
Audit ADR coverage across modules. Identifies modules with no architectural governance, orphaned ADRs referencing removed modules, and stale architecture docs. Classifies findings by severity.
| name | new-proposal |
| description | Create a new proposal (RFC) document. Use when proposing a change, new feature, or architectural decision that needs team review. Handles numbering, naming, and template population. Use --root for cross-cutting proposals that affect multiple modules. |
| allowed-tools | Read, Write, Bash(ls *), Bash(wc *) |
| user-invocable | true |
Create a new proposal (RFC) document with correct numbering, naming, and template content.
/new-proposal <short-title> [--module <path>] [--root]
| Argument | Required | Description |
|---|---|---|
<short-title> | Yes | Short, hyphenated title for the proposal (e.g., switch-to-event-sourcing) |
--module <path> | No | Target module path (e.g., packages/auth-service). Defaults to current module context. |
--root | No | Create a cross-cutting proposal at the repo root level (docs/proposals/) |
Parse arguments. Extract the short title from $ARGUMENTS. Determine the target:
--root: target is docs/proposals/ at the repo root--module <path>: target is <path>/docs/proposals/Get next sequence number. Run:
bash scripts/next-number.sh --dir <target-proposals-dir>
This returns the next available NNN (zero-padded to 3 digits).
Create the proposal file. Read the template from templates/proposal.md and create <target>/NNN-<short-title>.md.
Populate frontmatter:
| Field | Value |
|---|---|
title | Derived from the short title (humanized) |
number | The NNN from step 2 |
status | draft |
author | Git user name (git config user.name) or prompt user |
created | Today's date (YYYY-MM-DD) |
updated | Today's date (YYYY-MM-DD) |
supersedes | null |
superseded_by | null |
Pre-populate context. If the target is a module, read available module information (README, CLAUDE.md) to seed the Context section with relevant background.
Identify architecture impact. List any existing architecture docs in the module's docs/architecture/ directory that may need updating if this proposal is accepted.
Confirm creation. Report the created file path and remind the user of next steps:
/proposal-status NNN in-review/proposal-status NNN accepted (will prompt for ADR creation)The short title must follow these rules:
Good: switch-to-event-sourcing, add-payment-gateway
Bad: Switch_To_Event_Sourcing, add payment gateway
templates/proposal.md — RFC template (copy of scaffold/templates/core/proposal.md)scripts/next-number.sh — Determines the next NNN sequence number for a directory