AI Marketplaces Leaderboard

Development OS

ChatGPT plugin

Effectively create anything.

View in ChatGPT directory
Featured
No

not on the featured shelf

Movement

From our daily snapshots over the last 30 days.

Rank by placement

#5218of 6,022024h—7d
#5,171#5,315#5,459#5,603Sep 13Sep 19Sep 25Oct 1Oct 7Oct 12

Rank in Productivity

#1121of 1,3711places down24h—7d
#1,105#1,151#1,197#1,243Sep 13Sep 19Sep 25Oct 1Oct 7Oct 12

In its category

How this plugin compares with others in the same category. Positions are counted within the category, not across the whole directory.

Productivity1,121st of 1,371 by placement
#PluginPosition7d
1118X4◇M8§Q7·V3_Z9∆K6#5210—
1119Power BI Report Copilot#5212—
1120Talamus Memory#5215—
1121Development OSThis page#5218—
1122AIOS — Setup Windows#5219—
1123Dossaro#5222—
1124GPT vers Plugin · Le QG#5223—

All 1,371 Productivity plugins

Development OS provides five coordinated reasoning skills for software and digital-product work while remaining independent of any specific repository, provider, or connected tool.

Example prompts

  • “Use Development OS to inspect this software project.”
  • “Use Development OS to shape this feature before implementation.”
  • “Use Development OS to audit and improve this codebase.”

Skills

  • development-os

    Automatically use for software and digital-product development work. Own the active development session: fresh present intent, stable objective/constraints, stage and mode, authority, scoped authorization, referent-scoped liveness, capability routing, visible position, stewardship, and fresh-context reconstruction. Route product meaning to Founder-to-Feature, perspective to Specialist Reasoning, proof to Evidence Stewardship, and execution to Lean Repository Execution.

  • evidence-stewardship

    Automatically use whenever development work depends on proof, uncertainty, tests, runtime/provider evidence, documentation authority, regressions, acceptance, or deciding what evidence deserves permanence. Manage the transition from uncertainty to justified confidence and preserve durable guarantees without turning every probe into infrastructure.

  • founder-to-feature

    Automatically use when development work contains unresolved product meaning: substantial feature ideas, architecture-affecting behavior, workflow redesign, or audit findings that require deciding what should become true. Own Explore → Resolve → Crystallize → Ready for the semantic referent; do not own session state, proof permanence, or implementation mechanics.

  • lean-repository-execution

    Automatically use for authorized implementation, debugging, refactoring, repository/provider operations, verification, and delivery. Own orientation, canonical-owner changes, mutation integrity, execution cadence, verification cadence, recovery, provider operations, and completion while relying on Development OS for intent/authorization and Evidence Stewardship for proof permanence.

  • specialist-reasoning

    Automatically use when professional perspective or materially different representations could improve software/product work. Select the smallest sufficient professional team, reason independently before synthesis, distinguish evidence from inference, deliberately diverge before convergence on substantial conceptual work, and return only findings that materially change the owning workflow.

Categories
Made by
Development OS
Sign-in
On Install
Capabilities
Read
Availability
Available
Version
4.1.6
Keywords
software-development, development-os, reasoning, evidence, execution
Created
September 19, 2026