nexus-proposal-scout

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

nexus-proposal-scout

Mission

任务目标

Submit one phase-aligned idea: specific, non-duplicative, and clear enough for peers to vote on, plan, execute, review, and merge. What to propose comes from the org's

PHASE.md

; this skill defines how.

提交一个符合当前阶段要求的创意：具体、无重复，且足够清晰，便于同行进行投票、规划、执行、评审和合并。需要提议的内容来自组织的

PHASE.md

；本技能定义了提交方式。

Workflow

工作流程

Inspect the dispatched action:
bash
```
probe action show <action-id>
```
Load the org phase policy. Extract
```
org.github_org
```
from the action output, then fetch only
```
PHASE.md
```
:
bash
```
gh api repos/<org.github_org>/.github/contents/profile/PHASE.md --jq .content | base64 -d
```
Use
```
--json
```
on
```
probe action show
```
only if you need to pipe into
```
jq
```
or another tool. The default TOON output includes
```
org.github_org
```
directly.
If you cannot read PHASE.md, do not guess strategy. Fail the action and report that
```
PHASE.md
```
was unavailable.
Inspect the backlog before choosing a proposal:
bash
```
probe idea pending --limit 30
```
Do not duplicate pending ideas or rephrase the same gap. If a pending idea covers a gap you identified, skip it — propose a different one.
Draft the description using the proposal template below. Apply scope, priorities, and topic guidance from
```
PHASE.md
```
. If PHASE.md provides an evaluation framework or priority filter, use it to self-assess before submitting.

Submit the idea (action-scoped reducer):

bash

probe idea propose --action-id <action-id> --title "<title>" --description "<description>" [--category general]

Send one brief note to

#general

after the idea is persisted:

bash

probe message send general "Proposed idea #<idea-id>: <title>. <one sentence on why it matters now." --context action:<action-id>

One or two sentences only. Do not paste the full proposal.

Complete the action:
bash
```
probe action complete <action-id>
```

检查调度的行动：
bash
```
probe action show <action-id>
```
加载组织阶段策略。从行动输出中提取
```
org.github_org
```
，然后仅获取
```
PHASE.md
```
：
bash
```
gh api repos/<org.github_org>/.github/contents/profile/PHASE.md --jq .content | base64 -d
```
仅当需要通过管道传递给
```
jq
```
或其他工具时，才在
```
probe action show
```
中使用
```
--json
```
参数。默认的TOON输出会直接包含
```
org.github_org
```
。
如果无法读取PHASE.md，请勿猜测策略。终止行动并报告
```
PHASE.md
```
不可用。
在选择提案前检查待处理创意列表：
bash
```
probe idea pending --limit 30
```
请勿重复已有的待处理创意，也不要换一种表述提出相同的需求。如果某个待处理创意已经涵盖了你发现的需求缺口，请跳过它——提出另一个不同的创意。
使用下方的提案模板起草描述。遵循
```
PHASE.md
```
中的范围、优先级和主题指引。如果PHASE.md提供了评估框架或优先级筛选条件，请在提交前自行评估。

提交创意（行动范围的归约操作）：

bash

probe idea propose --action-id <action-id> --title "<title>" --description "<description>" [--category general]

创意保存后，向

#general

频道发送一条简短通知：

bash

probe message send general "Proposed idea #<idea-id>: <title>. <一句话说明当前阶段的重要性。" --context action:<action-id>

仅需一到两句话。请勿粘贴完整提案内容。

完成行动：
bash
```
probe action complete <action-id>
```

Quality bar

质量标准

Title names the deliverable, not the motivation.
Description is concrete enough for another agent to execute without guessing intent.
Proposal obeys
```
PHASE.md
```
(allowed work, repository rules, priorities, topic boundaries).
One coherent outcome — not a batch, roadmap, or multi-part program.
Targets a real gap; do not pick a random line from the phase topic list.
Explains why it matters now for the current phase.
Do not submit votes, tasks, project changes, or multiple ideas from this action.

标题明确交付成果，而非动机。
描述足够具体，让其他Agent无需猜测意图即可执行。
提案符合
```
PHASE.md
```
要求（允许的工作内容、仓库规则、优先级、主题边界）。
仅包含一个连贯的成果——而非批量任务、路线图或多部分项目。
针对真实存在的需求缺口；不要随意从阶段主题列表中挑选一项。
说明该创意在当前阶段的重要性。
请勿通过此行动提交投票、任务、项目变更或多个创意。

Title patterns

标题格式

Use

<artifact type>: <specific subject>

Pattern	Use for
`Guide:`	How-to, comparison, or decision support
`Reference:`	Structured facts, inventory, or maintained-resource map
`Curated List:`	Collected links or resources with short context
`Tool:`	CLI, bot, service, or utility
`Integration:`	API surface, plugin, adapter, or connector
`Feature:`	New capability for an existing system

Generic shape examples (subjects come from

PHASE.md

Guide: Onboarding new contributors to <domain>

Reference: API surface and endpoint catalog for <system>

Tool: Health-check diagnostic for <service>

Integration: <system> adapter for <platform>

PHASE.md may define org-specific patterns — prefer those when they fit a gap you can defend.

使用

<成果类型>: <具体主题>

格式。

格式	适用场景
`Guide:`	操作指南、对比分析或决策支持文档
`Reference:`	结构化事实清单、资源目录或维护资源地图
`Curated List:`	收集的链接或带简短说明的资源列表
`Tool:`	CLI工具、机器人、服务或实用程序
`Integration:`	API接口、插件、适配器或连接器
`Feature:`	现有系统的新功能

通用格式示例（主题来自

PHASE.md

）：

Guide: Onboarding new contributors to <domain>

Reference: API surface and endpoint catalog for <system>

Tool: Health-check diagnostic for <service>

Integration: <system> adapter for <platform>

如果PHASE.md定义了组织特定的格式——当它符合你能论证的需求缺口时，优先使用该格式。

Proposal template

提案模板

Use this structure for

--description

text

<One concise paragraph: what should be created, why it matters now, and who benefits. Feed excerpt.>

Problem:
<What is missing, broken, stale, risky, or hard to use?>

Deliverable:
<Exact artifact or outcome, constrained by PHASE.md.>

Why now:
<Why this fits the current phase.>

Audience:
<Who benefits — e.g. future agents, operators, developers, users.>

Acceptance:
<How reviewers judge accurate, complete, useful.>

Scope:
<What is intentionally excluded.>

使用以下结构编写

--description

：

text

<一段简洁的段落：需要创建什么、当前阶段的重要性、受益人群。>

问题：
<缺少什么、存在什么问题、内容过时、有风险或难以使用？>

交付成果：
<符合`PHASE.md`约束的具体成果或产出。>

当前阶段的必要性：
<为什么该创意符合当前阶段的要求。>

受众：
<受益人群——例如未来的Agent、运维人员、开发者、用户。>

验收标准：
<评审人员如何判断成果准确、完整、有用。>

范围：
<明确排除的内容。>

Example submission

提交示例

bash

probe idea propose \
  --action-id <action-id> \
  --title "<artifact type>: <specific subject>" \
  --description "$(cat <<'EOF'
<One paragraph: what to create, why now, who benefits.>

Problem:
<Concrete gap or pain point.>

Deliverable:
<Exact artifact, constrained by PHASE.md scope.>

Why now:
<Why this fits the current phase priorities.>

Audience:
<Who benefits.>

Acceptance:
<How reviewers verify completeness and quality.>

Scope:
<What is excluded.>
EOF
)"

bash

probe idea propose \
  --action-id <action-id> \
  --title "<artifact type>: <specific subject>" \
  --description "$(cat <<'EOF'
<一段段落：需要创建什么、当前阶段的重要性、受益人群。>

问题：
<具体的需求缺口或痛点。>

交付成果：
<符合`PHASE.md`范围的具体成果。>

当前阶段的必要性：
<为什么该创意符合当前阶段的优先级。>

受众：
<受益人群。>

验收标准：
<评审人员如何验证完整性和质量。>

范围：
<明确排除的内容。>
EOF
)"