gemini-thinking-protocol

Translate business intent into executable software using structured cognitive analysis.

261|119|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/kennyzir/7deer_skills --skill gemini-thinking-protocol
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gemini-thinking-protocol
Source: https://github.com/kennyzir/7deer_skills/tree/main/gemini-thinking-protocol
Command: npx skills add https://github.com/kennyzir/7deer_skills --skill gemini-thinking-protocol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Gemini Cognitive Engine Protocol converts user business intent into executable software by rigorously applying First Principles, dialectics, and systems thinking to ensure solutions are principled, robust, and scalable.

Core Features & Use Cases

  • PrincipledTransformation: Transforms vague business ideas into concrete software architecture and actionable requirements.
  • StructuredAnalysis: Uses four cognitive layers (First Principles, Dialectics, Systems Thinking, Critical Thinking) to surface trade-offs and risks.
  • Use Case: When a product asks for deep refactoring or new architecture under uncertain constraints, the engine provides a defendable, testable plan with evaluation criteria.

Quick Start

Describe your business scenario after activation, and I will distill it into executable software using principled reasoning.

Frequently Asked Questions about gemini-thinking-protocol

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I translate ambiguous business intent into executable software architecture?

Translate ambiguous business intent into executable software by applying First Principles, dialectics, and systems thinking to distill vague requirements into a defendable, actionable architecture plan.

What is the best way to approach system design under uncertain or contradictory constraints?

Approach system design under contradictory constraints by applying a cognitive engine that uses dialectics and systems thinking to surface trade-offs, evaluate risks, and generate a testable software plan.

Can I use first principles thinking to evaluate deep refactoring requirements?

You can use first principles thinking to evaluate deep refactoring by rigorously analyzing the architecture to ensure the proposed software transformation is principled, robust, and scalable.

How do I structure product strategy analysis to surface trade-offs and risks?

Structure product strategy analysis by applying four cognitive layers—First Principles, Dialectics, Systems Thinking, and Critical Thinking—to surface hidden trade-offs, mitigate risks, and enforce clear communication protocols.

Does this approach work for complex architecture design without specific framework dependencies?

This approach works for complex architecture design without framework dependencies because it operates as a cognitive engine protocol that processes business intent through principled reasoning rather than relying on specific platform implementations.