How do I install the Mk:bootstrap skill?

Run npx skillmds@latest add ngocsangyem/mk-bootstrap in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Mk:bootstrap safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Mk:bootstrap?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Mk:bootstrap free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Mk:bootstrap?

ngocsangyem (@ngocsangyem) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Mk:bootstrap by ngocsangyem — Agent Skill

Name: Mk:bootstrap
Author: ngocsangyem

Mk:bootstrap

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).

ngocsangyem 292a3de 11 files · 28.7 KB Updated Sep 17, 2026

File contents

Bootstrap

End-to-end project orchestrator: research → design → plan → scaffold → implement → docs.

CLI boundary: the installer = project infrastructure. mk:bootstrap = application code + full pipeline. Zero overlap. Never touch .claude/.

When to Use

Explicit only — never auto-activate.

mk:bootstrap [requirements]
mk:bootstrap [requirements] --full
mk:bootstrap [requirements] --fast
mk:bootstrap [requirements] --parallel

Do NOT invoke when: project already has source code, or you only need kit setup (use CLI).

Modes

Mode	Flag	Gates	Research	Design	Plan flag	Cook flag
Auto	(default)	Design only	Parallel researchers	UI/UX if frontend	`--auto`	`--auto`
Full	`--full`	Every step	Parallel researchers	UI/UX if frontend	`--hard`	(interactive)
Fast	`--fast`	None	6 parallel batch	Skip	`--fast`	`--auto`
Parallel	`--parallel`	Design only	Parallel researchers	UI/UX if frontend	`--parallel`	`--parallel`

Routing

Parse first flag from arguments:

--full → load references/workflow-full.md
--fast → load references/workflow-fast.md
--parallel → load references/workflow-parallel.md
default → load references/workflow-auto.md

Each workflow file defines the exact steps for that mode. After plan + scaffold, all modes load references/shared-phases.md for implementation → docs → final report.

Planning BEFORE Scaffolding

Plan first, scaffold second. The plan tells us WHAT to scaffold.

Plan — invoke mk:plan-creator with mode-matched flag. Plan defines: architecture, modules, file structure, acceptance criteria.
Scaffold — generate files following the plan's architecture + references/scaffolding-principles.md. Detect stack via scripts/detect-stack.sh. Validate with scripts/validate-bootstrap.sh.

Optional: invoke mk:plan-ceo-review on the plan (Full mode).

Planning is NOT optional. Every bootstrap creates a plan before generating any source files.

Gotchas (top 3)

Scaffolding before planning: generating files without a plan → plan first, scaffold second
Skipping research on "simple" projects: hidden complexity → always research unless --fast
Duplicating CLI init: never generate .claude/ files — CLI handles that

Full list: references/gotchas.md

Workflow Integration

Pre-workflow. Bootstrap IS the full workflow for new projects:

mk:bootstrap → [research → design → plan → scaffold → cook → docs] → done

For subsequent features on the same project: use mk:plan-creator → mk:cook directly.

---name: mk-bootstrapdescription: 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).---# BootstrapEnd-to-end project orchestrator: research → design → **plan → scaffold** → implement → docs.**CLI boundary:** the installer = project infrastructure. `mk:bootstrap` = application code + full pipeline. Zero overlap. Never touch `.claude/`.## When to Use**Explicit only** — never auto-activate.```mk:bootstrap [requirements]mk:bootstrap [requirements] --fullmk:bootstrap [requirements] --fastmk:bootstrap [requirements] --parallel```Do NOT invoke when: project already has source code, or you only need kit setup (use CLI).## Modes| Mode | Flag | Gates | Research | Design | Plan flag | Cook flag ||------|------|-------|----------|--------|-----------|-----------|| **Auto** | (default) | Design only | Parallel researchers | UI/UX if frontend | `--auto` | `--auto` || **Full** | `--full` | Every step | Parallel researchers | UI/UX if frontend | `--hard` | (interactive) || **Fast** | `--fast` | None | 6 parallel batch | Skip | `--fast` | `--auto` || **Parallel** | `--parallel` | Design only | Parallel researchers | UI/UX if frontend | `--parallel` | `--parallel` |## RoutingParse first flag from arguments:- `--full` → load `references/workflow-full.md`- `--fast` → load `references/workflow-fast.md`- `--parallel` → load `references/workflow-parallel.md`- default → load `references/workflow-auto.md`Each workflow file defines the exact steps for that mode. After plan + scaffold, all modes load `references/shared-phases.md` for implementation → docs → final report.## Planning BEFORE Scaffolding**Plan first, scaffold second.** The plan tells us WHAT to scaffold.1. **Plan** — invoke mk:plan-creator with mode-matched flag. Plan defines: architecture, modules, file structure, acceptance criteria.2. **Scaffold** — generate files following the plan's architecture + `references/scaffolding-principles.md`. Detect stack via `scripts/detect-stack.sh`. Validate with `scripts/validate-bootstrap.sh`.Optional: invoke `mk:plan-ceo-review` on the plan (Full mode).**Planning is NOT optional.** Every bootstrap creates a plan before generating any source files.## Gotchas (top 3)- **Scaffolding before planning**: generating files without a plan → plan first, scaffold second- **Skipping research on "simple" projects**: hidden complexity → always research unless `--fast`- **Duplicating CLI init**: never generate .claude/ files — CLI handles thatFull list: `references/gotchas.md`## Workflow IntegrationPre-workflow. Bootstrap IS the full workflow for new projects:```mk:bootstrap → [research → design → plan → scaffold → cook → docs] → done```For subsequent features on the same project: use `mk:plan-creator` → `mk:cook` directly.

Frequently asked questions