Menu
Implement a feature or fix from product/technical specs while checking the final code against the stated requirements.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Reduction-ladder and minimum-diff checks the Pythinker judge subagent applies to every non-trivial diff.
Over-engineering review checklist the parent runs before declaring non-trivial code changes done.
Whole-repo audit for over-engineering and accidental complexity. Scans the entire codebase (not just a diff) and returns a ranked, read-only list of what to delete, simplify, or replace with standard-library or platform equivalents. Use when the user asks to "audit the codebase", "find bloat", "what can I delete", or wants a repo-wide simplification pass. For a diff-scoped pass use `pythinker review diff --mode deslopify` instead. One-shot report; applies no fixes.
Prescriptive frontend design guidance via the designer-skill MCP server. Use when the user asks to use designer-skill, improve UI/UX, run the anti-slop ship gate, apply a design system, or enhance pages/components with MCP-backed design references โ especially for Pythinker docs and marketing surfaces with DESIGN.md/PRODUCT.md.
Author a new project-specific Pythinker subagent (a specialist like "migration-reviewer" or "api-contract-checker") with a correct spec, a persona-rich system prompt, and a structured output contract. Use when the user wants to create, scaffold, or design a custom agent / subagent, or asks how Pythinker agent YAML / markdown agent files, tool scoping, or the extend-inheritance schema work.
Edit Pythinker's own configuration โ agent YAML specs and extend-inheritance, the permission profiles that gate tools, plugin.json, and hook lifecycle events. Use ONLY when the user wants to configure, customize, or extend Pythinker itself (its agents, permissions, plugins, or hooks). For authoring a new agent use agent-creator; for authoring a skill use skill-creator; for general usage Q&A use pythinker-code-help.
| name | spec-driven-implementation |
| description | Implement a feature or fix from product/technical specs while checking the final code against the stated requirements. |
Use when the task references a product spec, tech spec, design doc, issue plan, or explicit acceptance criteria.
Return:
SUMMARY
SPEC REQUIREMENTS
CHANGES
SPEC CHECK
VERIFICATION
RISKS