Cluster detail
chat-participant.rq
Ideas defined in reqlan rq/extension/agent/chat-participant.rq.
file
4 ideas
1 files
| Idea | File | Status | Summary | Katz |
|---|---|---|---|---|
| chat_participant | reqlan rq/extension/agent/chat-participant.rq | the chat participant module should expose @ reqlan in vscode chat. it should consume analysis functions from the analytical submodule rather than duplicating graph logic. slash commands should use the rq- prefix only in chat, e. g. rq-search, rq-context, rq-graph, and rq-related for the active file. | 0.052 | |
| chat_participant_completion | reqlan rq/extension/agent/chat-participant.rq | file and requirement references should be code completed in the chat window via # file and # requirement language model tools. | 0.040 | |
| chat_participant_skills | reqlan rq/extension/agent/chat-participant.rq | the chat participant must not have duplicate skills. | 0.040 | |
| mcp | reqlan rq/extension/agent/chat-participant.rq | Cursor and other non-VS-Code clients use the MCP server ( `@reqlan/mcp` ). Search and retrieval on that server use ["./skills-and-mcp.rq".mcp_click_retrieval] only. Reference checks use ["./skills-and-mcp.rq".mcp_check]. The MCP tool set is not a 1: 1 wrap of every @ reqlan chat slash command. Published to npm per ["../../distribution/distribution.rq".npm_distribution]. Cursor project config lives in ["../../../.cursor/mcp.json"] and skills sync to ["../../../.cursor/skills"] via scripts / sync-cursor-ai. mjs. | 0.114 |
Cluster graph
Initialising graph…