menu-proposal

Menu Proposal Workflow

Review, customize, and allocate the native Telegram command menu for Ida.

Procedure

1. Sample Telemetry and Discover Capabilities

1. Sample recent invocations: Query execution telemetry spans (or inspect recent session logs) for skill runs and menu taps across interactive sessions and subagents to gather empirical invocation frequencies.
2. Discover candidate skills and workflows:
   • Enumerate installed skills across plugins (plugins/*/skills/) and common workflow templates.
   • Include operator-facing coordination skills (reify, dispatch, mine, reconcile, daily).
   • Strictly exclude reserved platform commands (start, help, status) and headless worker lifecycle commands (pull, dump).
3. Separate interactive menus from headless workers (headless-workers.md):
   • Telegram command menus exclusively serve interactive operator sessions. Headless worker lifecycle commands (pull, dump) must never appear on conversational menus or in candidate pools.
   • Autonomous workers operate non-interactively and cannot pause for human input; the menu proposal workflow is designed exclusively for interactive operator dialogue and must never be dispatched to a headless worker.
4. Inspect current allocations: Read the active TELEGRAM_BOT_COMMANDS list in the channel's $STATE_DIR/.env.

2. Synthesize Considered Recommendations

Apply qualitative judgment to evaluate candidate commands for the shared menu:

• Shared Menu Allocation: Prioritize high-frequency operational triage, quick capture, decision walk-throughs, task queueing, disambiguation, daily briefings, and worker dispatch (e.g. /decide, /q, /mine, /reconcile, /hydrate, /up, /reify, /dispatch, /daily).
• Composite commands: Propose single-tap composite commands where recurring multi-step patterns or common briefings are identified (such as /daily).
• Command identifier normalization & platform constraints:
  • Convert kebab-case skill and workflow names to valid Telegram command identifiers (snake_case) by replacing hyphens with underscores (e.g. strategic-review $\rightarrow$ /strategic_review, argument-map $\rightarrow$ /argument_map, menu-proposal $\rightarrow$ /menu_proposal, session-trace $\rightarrow$ /session_trace).
  • Ensure all command identifiers strictly match /^[a-z0-9_]{1,32}$/ (no hyphens, lowercase alphanumeric and underscores only, length 1–32).
  • Descriptions must be 1–256 characters, and total registered commands must not exceed 100.

3. Present Proposal Matrix

Present a scannable proposal table to the user (in interactive operator sessions only; headless workers cannot pause for human input):

• Candidate pool summary: Total candidates inspected and current allocations in the shared menu.
• Recommendation table:
  • Command: Normalized identifier matching /^[a-z0-9_]{1,32}$/ with hyphens converted to underscores (e.g. /reify, /strategic_review).
  • Type: skill, workflow, or composite.
  • Usage: Empirical invocation count from recent telemetry.
  • Proposed Inclusion: [Include], [Exclude], or [Optional].
  • Description: Clear functional summary.
  • Rationale: Why this command fits the shared menu.
• Interactive options: Present checkbox proposals or structured options allowing the user to approve recommendations or adjust allocations in free text.

4. Codify Approved Allocations

1. The menu is exactly the JSON list in TELEGRAM_BOT_COMMANDS; the plugin builds none of its own. Codify the approved command list as JSON into TELEGRAM_BOT_COMMANDS in the channel's environment configuration ($STATE_DIR/.env); it is registered at the next poller start.
2. Run test verification (cd plugins/ida-telegram && bun test test/commands.test.ts) to ensure command registration passes cleanly.
3. Confirm updated menu to the user.