메뉴
Synthesize the settled conversation into a thin Plan on the work-tree leaf doc — no interview. Use when intent is pinned and you need a durable plan before building; helm's Plan phase reaches for this when the goal fits in one change.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/asteasolutions/ai-toolkit --skill to-spec명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
Grounded research. Traceability-first research workflow for evidence, reliability, product, policy, technical, sentiment, complaint, review, public-opinion, and source-backed questions. Use when the user asks for grounded research, rigorous research, exact source traceability, text fragment links, citations, verification, fact-checking, adversarial review, counterevidence, confidence labels, source hierarchy, or a claim-to-source evidence map. Also use when another skill needs source-backed claims checked against primary sources, current product/tool information, community sentiment, or contested evidence.
Evidence discipline for factual claims. Receipts before claims, no guessing, unknown is an allowed answer. Use as the baseline standard when citing sources, files, or command output, and when the user asks you to re-check an answer you already gave because they cannot verify it themselves.
use when the user wants a simple worded reply, or expresses that your speech is too complex, jargon-heavy, hard to understand etc. Or when they say "keep it simple"
| name | to-spec |
| description | Synthesize the settled conversation into a thin Plan on the work-tree leaf doc — no interview. Use when intent is pinned and you need a durable plan before building; helm's Plan phase reaches for this when the goal fits in one change. |
Turn settled conversation into a thin Plan. Do not interview — grilling already happened; capture what was decided.
Shapes match helm's work-tree artifacts (see helm/references/artifacts.md if present).
.scratch/<goal-slug>/ — this is the program counter.docs/agents/issue-tracker.md exists, follow its GitHub conventions for that mirror.Orient if needed. If the touched area isn't already understood, explore it. Prefer any domain vocabulary / decision docs the repo already has; discover them — don't invent a layout.
Sketch test seams. Prefer existing seams; pick the highest seam that still exercises the behaviour; minimise their number (ideal: one). Check seams with the developer before writing.
Write a thin Plan into the leaf doc:
.scratch/<goal-slug>/task.md## Plan section.Thin Plan contents only:
done criteriaNo brittle file paths or code. Exception: a decision-encoding prototype (schema, type, state machine) may be inlined when the shape is the decision.
Ask once about extras. After the thin Plan is written, ask whether to also include any of: user stories, out of scope, further notes (or other sections the developer names). Default is no. Add only what they pick.
GitHub mirror (opt-in). If publishing to GitHub, create/update the issue from the same Plan body. Local remains source of truth for resume.
# <feature title>
## Intent
<what + why>
## Plan
<what/why · test seams · implementation decisions · behaviour-level done criteria>
<!-- optional extras only if the developer asked for them -->