triage-then-detail — Feranor Resilience MCP Prompt

triage-then-detail is one of 3 prompts on the Feranor Resilience MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke triage-then-detail from your client

• Claude Code Feranor Resilience Prompt/triage-then-detail run in your project directory
• Claude Desktop Feranor Resilience Prompt/triage-then-detail ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor Feranor Resilience Prompt/triage-then-detail ~/.cursor/mcp.json
• VS Code Feranor Resilience Prompt/triage-then-detail .vscode/mcp.json
• Zed Feranor Resilience Prompt/triage-then-detail ~/.config/zed/settings.json
• Windsurf Feranor Resilience Prompt/triage-then-detail ~/.codeium/windsurf/mcp_config.json
• Cline Feranor Resilience Prompt/triage-then-detail ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI Feranor Resilience Prompt/triage-then-detail ~/.gemini/settings.json
• Grok Feranor Resilience Prompt/triage-then-detail .mcp.json (in your project root)
• ChatGPT Feranor Resilience Prompt/triage-then-detail Settings → Connectors → Advanced → Developer mode
• Claude.ai Feranor Resilience Prompt/triage-then-detail Settings → Connectors → Add custom connector
• LangChain Feranor Resilience Prompt/triage-then-detail pip install langchain-mcp-adapters

Other prompts on this server

• audit-portfolio
• verify-deployment

Feranor Resilience also offers 3 resources — data you attach as context, where a prompt is something you run.

Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026. A listing does not declare its prompts, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each prompt's arguments.