Cougr: Skill for Claude Code

Advanced Elicitation

Goal: Push the LLM to reconsider, refine, and improve its recent output.

---

CRITICAL LLM INSTRUCTIONS

• MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER
• DO NOT skip steps or change the sequence
• HALT immediately when halt-conditions are met
• Each action within a step is a REQUIRED action to complete that step
• Sections outside flow (validation, output, critical-context) provide essential context - review and apply throughout execution
• YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the communication_language

---

INTEGRATION (When Invoked Indirectly)

When invoked from another prompt or process:

1. Receive or review the current section content that was just generated
2. Apply elicitation methods iteratively to enhance that specific content
3. Return the enhanced version back when user selects 'x' to proceed and return back
4. The enhanced content replaces the original section content in the output document

---

FLOW

Step 1: Method Registry Loading

Action: Load ./methods.csv for elicitation methods. If party-mode may participate, resolve the agent roster via:

python3 {project-root}/.stellar-build/scripts/resolve_config.py --project-root {project-root} --key agents

The resolver merges four layers in order: .stellar-build/config.toml (installer base, team-scoped), .stellar-build/config.user.toml (installer base, user-scoped), .stellar-build/custom/config.toml (team overrides), and .stellar-build/custom/config.user.toml (personal overrides). Each entry under agents is keyed by the agent's code and carries name, title, icon, description, module, and team.

CSV Structure

• category: Method grouping (core, structural, risk, etc.)
• method_name: Display name for the method
• description: Rich explanation of what the method does, when to use it, and why it's valuable
• output_pattern: Flexible flow guide using arrows (e.g., "analysis -> insights -> action")