negotiated-decision-framework
Negotiated Decision Framework (NDF)
Purpose: Navigate multi-stakeholder decisions where different parties have legitimate but competing interests. NDF helps find decisions that stakeholders can live with, even if no one gets everything they want.
When to Use NDF
Use NDF when:
- Multiple stakeholders must agree (or at least not block)
- Different parties have different success criteria
- Power dynamics or politics affect the decision
- Past decisions created winners/losers who remember
- "Best technical answer" won't get adopted due to stakeholder resistance
- Need buy-in for implementation success
Don't use NDF when:
- Single decision-maker with clear authority (use ToT)
- Stakeholders agree on criteria (use ToT with shared criteria)
- Conceptual tension, not stakeholder tension (use DR)
- Time pressure prevents negotiation (use RTR, negotiate later)
More from kimasplund/claude_cognitive_reasoning
self-reflecting-chain
Sequential reasoning with deep self-reflection and backtracking. Use when problems have step-by-step dependencies, need careful logical reasoning, or require error correction. Each step includes self-reflection, and incorrect steps trigger backtracking. Ideal for debugging, mathematical proofs, sequential planning, or causal analysis where order matters.
95agent-memory-skills
Self-improving agent architecture using ChromaDB for continuous learning, self-evaluation, and improvement storage. Agents maintain separate memory collections for learned patterns, performance metrics, and self-assessments without modifying their static .md configuration.
44chromadb-integration-skills
Universal ChromaDB integration patterns for semantic search, persistent storage, and pattern matching across all agent types. Use when agents need to store/search large datasets, build knowledge bases, perform semantic analysis, or maintain persistent memory across sessions.
42integrated-reasoning
Meta-orchestration guide for choosing optimal reasoning patterns. Analyzes problem characteristics and recommends which cognitive methodology to use - tree-of-thoughts (find best), breadth-of-thought (explore all), self-reflecting-chain (sequential logic), or direct analysis. Use when facing complex problems and unsure which reasoning approach fits best.
30document-writing-skills
Teaches document writing patterns and templates that agents apply when generating documentation, reports, contracts, guides, and technical writing. Use when creating API docs, user guides, reports, changelogs, ADRs, or technical documentation.
23error-handling-skills
Universal error handling, exception management, and logging best practices for all development agents across JavaScript/TypeScript, Python, Rust, Go, and Java. Use when implementing error handling, exception management, logging, error recovery, or debugging production issues.
20