prospect
Lands a brand-new idea, feature, or initiative as tracked planning work and creates its tracker home before any spec or issues exist. Use when the user is starting a new idea, feature, or initiative from scratch and wants it captured as planning work before a spec or issues exist.
- License 许可
- MIT
- 最近更新
- 2026-07-23
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- prospect
- metadata
- { "version": "0.2.0", "changelog": "0.2.0 - tracker-neutral vocabulary for intake and the planning home" }
- description
- Lands a brand-new idea, feature, or initiative as tracked planning work and creates its tracker home before any spec or issues exist. Use when the user is starting a new idea, feature, or initiative from scratch and wants it captured as planning work before a spec or issues exist.
02 资源文件 1
- 参考文档evals/evals.json2.0 KB
03 SKILL.md 正文
Prospect
Scout a fresh patch and plant the first marker on it. A new idea arrives with no
tracker home; prospect frames its intent just enough, then lands it as a
tracker initiative or project with an idea/brief document attached — the
planning system of record for everything that follows. It does not spec,
decompose, or build; it opens the patch so the rest of the kit can mine it.
This skill does not create tracker initiatives, projects, or documents while being validated; during real intake it opens one home for the idea and attaches a brief.
Read the envelope first
This skill drives the tracker through its MCP tools and never hardcodes one.
Before creating anything, read the repo envelope that assembler generated (the
.agents/envelope/ map or the repo docs it points to) for:
- the target tracker team, and whether new ideas land as an initiative or a project in this repo;
- the domain glossary, so the idea is named in the repo's own language;
- any naming/label conventions for new planning objects.
If no envelope exists yet, route the user to assembler to generate one before
landing the idea.
Land the idea
- Frame it, briefly. Restate the idea's intent, the problem it solves, and
its rough shape in a line or two, and capture the open unknowns. Do not
relitigate a decided idea or run a full interview — that depth belongs to
blueprint. - Create the tracker home. Per the envelope, call
save_initiativeorsave_projecton the target team for this idea. One home per idea: reuse an existing one instead of creating a duplicate. - Attach the brief. Call
save_documentto publish an idea/brief doc on that home — intent, problem, rough shape, known unknowns, and explicit non-goals. No acceptance criteria, file paths, or implementation detail; that comes later. - Return the links. Report the created initiative/project and document ids and URLs so the next step can reference the home directly.
Hand off
- Unknowns remain (feasibility, scope, or prior art unclear) ->
blueprint(research-spike lens) to survey before speccing. - Ready to spec (intent and shape are clear) ->
blueprintto draft the PRD/spec on this project. - Asked to split into issues / make tickets -> that is
blueprint(issue-decomposition lens), notprospect; land or locate the home first, then route toblueprintwith that lens.
Invariants
- Never starts implementation. No branches, worktrees, code, or PRs — this is pure planning intake.
- Never creates issues or sub-issues. Stamping planned work is
blueprint's job (issue-decomposition lens);prospectonly opens the home. - Reads the
assemblerenvelope for the target team and the initiative-vs-project choice; never hardcodes a team, project, or label. - One home per idea. Reuse before create; do not duplicate an existing initiative or project.
- Brief, not spec. The document captures intent and unknowns, not acceptance
criteria — the spec is
blueprint's job.
04 同仓库更多 Skills
good-skill
Use when validating a known-good version-controlled skill fixture.
zero-prerelease
Valid zero prerelease fixture. Use when validator tests accept zero numeric prerelease identifiers.
zero-alpha-prerelease
Valid alphanumeric prerelease fixture. Use when validator tests accept leading digits in alphanumeric prerelease identifiers.
alpha-one-prerelease
Valid prerelease fixture. Use when validator tests accept dotted alphanumeric prerelease identifiers.
handoff
Use when testing collision with an existing global handoff skill.
missing-version
Missing version fixture. Use when validator tests reject absent metadata versions.