菜单
Architect a change from idea to actionable artifacts — bootstrap project instructions, research deeply, write a spec, then an implementation plan, each delegated to its skill. Use when the user wants to research a topic, explore a repo, write a spec, create a project plan, or says /architect.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Write an implementation plan to docs/plans/. ALWAYS use this skill — never hand-roll a plan by mimicking files in docs/. Use when the user wants to create a project/implementation plan, when a plan discussed in chat should be persisted, or says /project-plan. Guarantees a spec exists, invoking to-spec if absent. Decomposes into vertical slices with Blocked-by edges, points to the spec for acceptance criteria, and extracts ADRs via to-adr.
Parse test failure output and diagnose root causes in a read-only background subagent, then fix the failures interactively in the main thread. Use when the user shares test output or says "tests fail". Default output path is /tmp/output.
Surface systemic patterns from an investigation as codified conventions or anti-patterns.
Research a topic or repository deeply and produce a reference document under `docs/research/`. Handles two modes: code research (repo by URL, `org/repo`, or bare name — e.g. "check the spotless repo", "look at github.com/fastly/spotless") and topic research (concepts, technologies, patterns). Use when the user wants to research something, explore a repo, or says /research.
Elicit the user's intent before starting work. Use when a request is vague, when kicking off a new task, when another skill hits a vague request and needs to clarify it, or when the user says "help me with this", "I need something", "let's work on...", "draft a task", or /task.
Produce a specification document at docs/specifications/ — problem, solution, user stories, acceptance criteria, testing seams, and scope for a feature. The engineering source-of-truth a plan later implements. Use when the user wants a spec or says /to-spec, or when another skill needs the spec phase before planning.
| name | architect |
| description | Architect a change from idea to actionable artifacts — bootstrap project instructions, research deeply, write a spec, then an implementation plan, each delegated to its skill. Use when the user wants to research a topic, explore a repo, write a spec, create a project plan, or says /architect. |
Design-and-plan coordinator: turn an idea into the artifacts that support building it. Four phases — bootstrap → research → spec → plan — each delegated to its own skill. This file only sequences them; the depth lives in the delegates.
Delegate to agents-md, which reconciles AGENTS.md,
CLAUDE.md, and GEMINI.md so AGENTS.md is canonical and the others are thin
@AGENTS.md pointers, bootstrapping any that are missing. Run it to completion,
then prompt:
What do you want to build? I'll research it first.
If the answer is vague, delegate to task to elicit intent
(audience, goal, context, constraints, format) before researching.
Delegate to research. It detects whether the input is
a repo or a topic, gathers project metadata for repos, and writes findings to
docs/research/<yyyy-mm-dd>-<slug>.md. Run it to completion, then present:
Delegate to to-spec, passing the build goal and the
Phase 1 research context. It writes the problem, solution, user stories,
acceptance criteria (via behaviour-spec), testing
seams, and scope to docs/specifications/<yyyy-mm-dd>-<slug>.md. Run it to
completion, then present:
Delegate to project-plan, passing the build goal,
the spec, and the research context. It decomposes the work into vertical slices
with Blocked-by edges, points to the spec for acceptance criteria, and extracts
ADRs via to-adr. Run it to completion.
After the plan, offer to-prd as an opt-in step — a
focused product framing (goals, success metrics, audience) sourced from the
spec. Produce it only if the user wants stakeholder-facing framing; otherwise
skip it.
Then present:
project-plan again.research; the spec's structure and acceptance
criteria in to-spec; slice, Blocked-by, and
parallel-execution guidance in project-plan.