ULTRATHINK

Analyze codebases and market conditions without editing code.

Updated Nov 27, 2025
One-click install
npx skills add https://github.com/jadenmubaira-oss/POLYPROPHET --skill ultrathink-jadenmubaira-oss
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ULTRATHINK
Source: https://github.com/jadenmubaira-oss/POLYPROPHET/tree/main/.agent/skills/ULTRATHINK
Command: npx skills add https://github.com/jadenmubaira-oss/POLYPROPHET --skill ultrathink-jadenmubaira-oss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, paranoia-driven analysis mode for AI to deconstruct codebases and market conditions without editing code, ensuring governance and auditability.

Core Features & Use Cases

  • Deep contextual analysis of large codebases and market data to reveal hidden structure and risk.
  • Enforces safety and compliance checks, including mandatory briefs and live-data verification before reporting findings.
  • Produces guidance artifacts such as implementation plans and forensic notes to inform human decision-making.

Quick Start

Read the ULTRATHINK and EXECUTION skill frontmatter, then read the repository README. Start every response with the mandated BRIEF header and verify live data via /api/health before presenting any conclusions. Use the LIVE SERVER MONITORING workflow to document findings and update README at session end.

Frequently Asked Questions about ULTRATHINK

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

FAQPage Schema
How do I analyze a codebase to generate audit-ready guidance without modifying the source code?▼

You can analyze a codebase without modifying code by using a paranoia-driven analysis mode that inspects repository manifests and protocol documentation to generate trustworthy, audit-ready guidance artifacts.

What is the process for verifying live market data before reporting metrics in an AI analysis workflow?▼

Verifying live market data requires enforcing rigorous sanity checks and live-data verification via endpoints like /api/health before the analysis workflow reports any metrics or conclusions.

How do I enforce safety and compliance checks when deconstructing large codebases for hidden risks?▼

To enforce safety and compliance checks when deconstructing codebases, apply mandatory BRIEF protocols and sanity checks that generate forensic notes and implementation plans for human review.

Does codebase analysis require a specific environment setup or prerequisite protocols to start?▼

Codebase analysis requires reading repository READMEs and specific frontmatter rules to establish a baseline, followed by starting every response with a mandated BRIEF header before presenting conclusions.

What are the limitations of analyzing market conditions and codebases without editing the underlying files?▼

The limitation of non-editing analysis is that it strictly produces guidance artifacts like forensic notes and implementation plans to inform human decision-making rather than autonomously resolving the identified risks.