원클릭으로 Manus에서 모든 스킬 실행

express

스타9

포크3

업데이트2026년 7월 18일 02:14

One-pass ideation for well-understood work: the exact same evidence-gated interview as ideation, then ONE consolidated confirmation (scope tier + run mode), then contract and specs generated without per-artifact approval loops and executed immediately on an isolation branch. Use when the user says 'express ideation', 'one-shot this', 'interview me then just build it', or wants planning that flows straight into execution without reviewing the contract. For exploratory or unfamiliar territory, prefer the full ideation skill — per-artifact review gates earn their keep there.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

nicknisi

nicknisi/ideation

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Express Ideation

Express is a pre-commit of /ideation's post-interview routing — same interview, same critics, same artifacts (contract-data.json, specs, generator-rendered contract.html + contract.md via --md-output); the only difference is that the express finish is chosen here, up front, instead of at the routing question.

Clean-tree check — now, before the interview. Run git status --porcelain. Uncommitted changes would ride along on phase commits, and stopping costs one question here, not a completed interview. Dirty tree → ask: stash/commit first, accept the risk, or abort. A clean tree proceeds silently.
Run ideation. Read and follow ${CLAUDE_PLUGIN_ROOT}/skills/ideation/SKILL.md end to end with the routing question pre-answered to "Approve — express finish" (fold the run-mode question into the approval call, and skip the routing-time clean-tree check — it already ran above). Everything else — branch handling, resume semantics, strict fail-closed execution, completion lines — lives in ideation's Express finish path, the single owner of express semantics.
Scope guard (advisory). For exploratory or unfamiliar work, recommend the full /ideation flow instead — its evidence-derived routing recommendation makes the same call, with reasons.

이 저장소의 다른 Skills

같은 저장소

autopilot

nicknisi/ideation

Orchestrate full execution of an ideation project — reads the contract, builds an execution manifest, and runs all phases on the deterministic Workflow engine (parallel for independent phases, sequential for dependent ones). Auto-continues on success, gates on failure. Use after ideation is complete and specs are approved.

2026-07-189

execute-spec

nicknisi/ideation

Execute an implementation spec generated by ideation. Invokes Scout for codebase exploration, builds components with feedback loops, then runs a Verify-Review-Fix cycle with the Reviewer agent before committing.

2026-07-189

get-goal-prompt

nicknisi/ideation

Generate a /goal command that runs an ideation project to completion UNATTENDED by driving /ideation:autopilot. The /goal is a durability wrapper — it keeps autopilot going across hours/sessions and recovers from failures, while autopilot's Workflow engine does the dependency-ordered dispatch. Reads the contract, builds the /goal, copies it to the clipboard, and prints it. Use when the user says 'goal', 'run as goal', 'goal prompt', or wants to run the project long-haul/unattended rather than watching /ideation:autopilot interactively.

2026-07-189

ideation

nicknisi/ideation

You MUST use this before building any new feature, planning a migration, designing a system, or turning a decided-on idea into a plan. Triggers on: feature requests, project ideas, brain dumps, 'help me plan,' 'spec this out,' 'interview me,' 'I want to build,' 'let's design,' or any unstructured idea you're ready to turn into code. Covers small single-spec projects through multi-phase initiatives. Runs a conversational interview, writes an interactive HTML contract, then generates implementation-ready Markdown specs. This is the planning-HOW stage: if the user is still deciding WHETHER to build — weighing options, pressure-testing a rough idea, 'should I…' — that's the lighter-weight brainstorming skill, and ideation takes over once they've committed to build. Skip ONLY for well-defined implementation tasks (writing code to a known spec, fixing bugs, refactoring, explaining code).

2026-07-189

retro

nicknisi/ideation

Mine a completed ideation project's implementation notes for generalizable spec-gap patterns and append them to a repo-level docs/ideation/learnings.md, so future interviews and specs learn from past gaps. Reads the project's implementation-notes-phase-*.html, contract.md, and git history; keeps only patterns that would change how future specs or interviews are written; dedupes against existing entries and retires entries the current codebase has invalidated. Use when the user says 'retro', 'run a retro', 'what did we learn', or after an ideation project completes.

2026-06-119

name	express
description	One-pass ideation for well-understood work: a thin alias that pre-commits /ideation's post-interview routing to the express finish. Identical evidence-gated interview, one consolidated confirmation (scope tier + run mode), then contract and specs generated without per-artifact approval loops and executed immediately on an isolation branch. Use when the user says 'express ideation', 'one-shot this', 'interview me then just build it', or wants planning that flows straight into execution without reviewing the contract. For exploratory or unfamiliar territory, prefer the full ideation skill — per-artifact review gates earn their keep there.
disable-model-invocation	true
allowed-tools	["Read","Write","Edit","Bash","Glob","Grep","Agent","AskUserQuestion","Workflow","TaskCreate","TaskUpdate","TaskList","TaskGet"]

Express Ideation

Clean-tree check — now, before the interview. Run git status --porcelain. Uncommitted changes would ride along on phase commits, and stopping costs one question here, not a completed interview. Dirty tree → ask: stash/commit first, accept the risk, or abort. A clean tree proceeds silently.
Run ideation. Read and follow ${CLAUDE_PLUGIN_ROOT}/skills/ideation/SKILL.md end to end with the routing question pre-answered to "Approve — express finish" (fold the run-mode question into the approval call, and skip the routing-time clean-tree check — it already ran above). Everything else — branch handling, resume semantics, strict fail-closed execution, completion lines — lives in ideation's Express finish path, the single owner of express semantics.
Scope guard (advisory). For exploratory or unfamiliar work, recommend the full /ideation flow instead — its evidence-derived routing recommendation makes the same call, with reasons.