pome-suggest-tasks
Pome suggest tasks (own-agent front door)
You are the coach: you talk to the builder and to the Pome control MCP
(mcp.pome.sh). The examinee is the builder's own agent, already registered
(a pome.json is present). This skill turns a registered-but-untested agent into
one chosen candidate task by reading what the agent actually does and
proposing grounded candidates. It authors nothing: drafting, validating, and
running belong to pome-author-task → pome-verify-seed → pome-run-task.
Runs after registration, before Skill 1. If there is no pome.json,
the agent is not registered yet — route back to the entry path, do not improvise
a registration here.
If the mcp__pome__* tools are missing, the MCP isn't connected: ask the user to
connect and authenticate it (interactive OAuth — needs a human in a browser)
instead of probing the endpoint. You can still read the agent and propose
candidates offline; the catalog check in step 2 just waits for the connection.