21건 · 관련도순
Use when invoked as $new-project or when creating a brand-new repository or project from scratch — scaffolds mise-pinned tools, a just task surface, the standard repo files, and CI for Python (uv), TypeScript (bun), Rust (cargo), or Go.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user adds a project to the workspace, opens an unfamiliar repo, asks "what is this project", "explain this codebase", or invokes explain-new-project. Explores a newly opened workspace project and writes a plain-language report for a self-taught, non-technical user—quick start (what it is + how to run) first, then optional depth—and always saves PROJECT_GUIDE.md in the project root.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Set up a new project by gathering context, optionally researching the domain, defining requirements, and building a roadmap. It creates planning files that record the project’s background, workflow preferences, phased structure, and ongoing state.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Turn an initial research idea into a project specification through a structured interview. Develop testable questions, hypotheses, methods for identifying causal effects, and data requirements, then rank options by feasibility and contribution and save the plan.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Initialize a new project with deep context gathering and PROJECT.md
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Scan a repo for mixed ADRs, PRDs, SPECs, and DOCs and bootstrap or merge the full .planning/ setup from them. Classifies each doc in parallel, synthesizes a consolidated context with a conflicts report, and routes to new-project or merge-milestone depending on whether .planning/ already exists.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Add one bounded feature to an existing app while preserving current behavior. Do not restart the full new-project workflow.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implement a new-project slice through the relevant checks and working user journey.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when you need an isolated copy of one or more repos with its own .planning/, or want to work on several repos in parallel. Creates worktrees or clones plus WORKSPACE.md; then run /gsd-new-project inside.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when onboarding to an unfamiliar codebase, before a major refactor, on a brownfield project before /gsd-new-project, or to refresh .planning/codebase/. Spawns up to 4 parallel mapper agents that write 7 documents.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when starting GSD in a repo that has no .planning/ yet, or the user wants a new project set up. Questioning, optional research, requirements, and roadmap produce .planning/PROJECT.md, REQUIREMENTS.md, ROADMAP.md, and STATE.md.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Initialize a new project with deep context gathering and PROJECT.md
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Scan a repo for mixed ADRs, PRDs, SPECs, and DOCs and bootstrap or merge the full .planning/ setup from them. Classifies each doc in parallel, synthesizes a consolidated context with a conflicts report, and routes to new-project or merge-milestone depending on whether .planning/ already exists.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a project has no docs/ directory or needs initial documentation generated from codebase analysis. Triggers on "init docs", "create documentation", "generate docs", "docs init", or when docs/ is empty. Do NOT use for updating existing docs (use mk:document-release).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when creating a new project from scratch — orchestrates the full journey from idea to running code. Research → design → plan → scaffold → implement → docs. Explicit invocation only — never auto-activates. CLI = project infrastructure (.claude/), bootstrap = application code + full pipeline. NOT for autonomous multi-hour builds of specified products (see mk:autobuild); NOT for single-task feature work on existing projects (see mk:cook).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when returning to a repo after a break, asking what changed, what's new for this stack, or invoking project-catch-up after explain-new-project. Scans the stack for important updates, deprecations, new helper tools, agent skills, and MCP servers online—plain-language brief saved as PROJECT_CATCH_UP.md.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run on an existing project to decide KEEP / MERGE / ARCHIVE — never limbo. Forces a call on tools that already exist and may have stopped earning their keep. Trigger on "is this still worth keeping", "audit this repo", "tech-debt cleanup", "sweep the folder", "what's dead here", or any signal that something hasn't been touched in months. Judged from both the agent lens (still legible, still drivable, still safe) and the human lens (do I still reach for it, does it nag). Includes a non-negotiable footgun check for stale pipelines that can overwrite live data. Outputs a backed AUDIT.md and a one-line verdict note in the project root docs. Do NOT load for greenfield projects (use new-project-gate), one-off bug fixes, or when the answer is already obvious.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run before building anything new — a pre-build gate that decides whether an idea deserves its own tool, judged from both the agent lens (legible, drivable, automatable) and the human lens (will I touch it, do I want to maintain it). Trigger on "should I build X", "starting a new project / app / tool / repo", "is this worth making", "want to spin up", or any new-build intent — even if the word "checklist" never appears. Outputs a backed GATE.md with checkmarks and a one-line verdict note in the project root docs. Do NOT load for small config tweaks, one-off scripts, bug fixes on existing things, or anything that is clearly a feature of something you already run.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user wants the full package on a repo, says run my project workflow, project check-in, or is overwhelmed opening an old or new folder. Runs the project onboarding checklist—explain-new-project, project-worth-my-time, and project-catch-up—in order or on demand.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use after PROJECT_GUIDE.md exists, when the user asks if a project is worth their time, should they build vs buy, or invokes project-worth-my-time. Follow-up to explain-new-project—weighs project context (files, git history, chat) to recommend whether to invest in a repo, cherry-pick a feature, park the idea, pass, or use an existing polished product instead. Optionally enriched by a personal-memory MCP (e.g. Pieces) when one is available.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Initialize a new project with deep context gathering and PROJECT.md
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.