Skip to main content
All projects

Open-source developer tooling

GodPrompt

One engineering workflow. Two delivery layers.

GodPrompt turns recurring software-engineering discipline into a reusable agent workflow: classify the task, understand the codebase, plan the smallest change, execute with the right protocol, verify the evidence, then report what actually happened.

Released · MIT licensed

9
task types
7
MCP tools
2
open-source repos
MIT
license

Architecture

The workflow and the transport stay separate.

01

GodPrompt core

The core repository contains the always-on skill, deeper protocols, verification gates and anti-pattern guidance. A combined GodPrompt.md remains available for environments that prefer one file.

  • Routes BUILD, DEBUG, REFACTOR, CONTENT, DESIGN, SHIP, ANALYZE, AUTOMATE and PLAN tasks.
  • Keeps the universal rules in the hot path and loads deeper guidance only when it is useful.
  • Can be used through repository/project instructions without requiring an MCP client.
02

GodPrompt MCP

The companion TypeScript server exposes the same workflow through Model Context Protocol instead of duplicating the content into a second system.

  • Seven tools expose the core skill, protocols, gates, anti-patterns, task classification and version metadata.
  • Supports local stdio and is listed on Glama for MCP discovery.
  • Generated content is synchronized from the core repository and covered by an MCP initialization/tool-list test.

Execution model

A bounded path from request to evidence.

  1. 01

    Classify

    Identify the task type and select the relevant protocol.

  2. 02

    Understand

    Read the code and dependencies before changing behavior.

  3. 03

    Plan

    Define scope, files, risks and verification before implementation.

  4. 04

    Execute

    Apply the task-specific workflow, including TDD where appropriate.

  5. 05

    Verify

    Run the checks that can actually prove the change works.

  6. 06

    Deliver

    Report the change, evidence, limitations and rollback path.

Progressive disclosure

Keep the base context small. Load depth when the task earns it.

The architecture separates the compact always-on skill from deeper protocol, gate and anti-pattern references. MCP clients can request the same pieces independently, while the full combined payload is still available for environments that need a single artifact.

Source & distribution