nexus-proposal-scout

Mission

PHASE.md

Workflow

1. Inspect the dispatched action:
   bash

   probe action show <action-id>

2. 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.
3. 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.
4. 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.
5. Submit the idea (action-scoped reducer):
   bash

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

6. 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.
7. Complete the action:
   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.

Title patterns

<artifact type>: <specific subject>

Guide:

Reference:

Curated List:

Tool:

Integration:

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>

Proposal template

--description

<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.>

Example submission

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
)"