Skill Claude CodeCodex
Point wise at a scope — a folder, a component, or the whole project — with a free-form improvement intent ("make the API faster", "pay down debt in src/auth", "raise test coverage", or just "improve this"), and it investigates the code read-only, decides what is worth doing, and writes self-contained implementation…
Skill Claude CodeCodex
Autonomously simplify recently-modified code and commit it — dispatches the code-simplifier agent over the working tree (cleanup only, behaviour preserved: clarity, consistency, dead-code/redundancy removal), then drafts a Conventional-Commits subject and commits. The lightweight per-commit tier of the plugin's…
Skill Claude CodeCodex
Scaffold a new skill inside the wise plugin by delegating to Claude Code's skill-creator skill. The new skill lands in plugins/wise/skills/ /. The plugin hosts two skill shapes: standalone slash-command skills and reference/guidance skills. Any free-form tail the user types after the skill name is forwarded to…
Skill Claude CodeCodex
Edit an existing wise plugin skill by delegating to Claude Code's skill-creator skill with the existing SKILL.md as the target and the wise plugin conventions as guardrails. Locates the skill under plugins/wise/skills/. Refuses the wise natural-language helper (editing it changes the plugin's discovery surface and…
Skill Claude CodeCodex
Attach a supervisor / watchdog loop to a running team of background agents and keep them on task — automates the manual "ping all your subagents, are you still on track?" nudge. Reads the team's members, actively probes each for its status, nudges any that are idle-but-unfinished or off-goal, and escalates a worker…
Skill Claude CodeCodex
Ticket-writing rules for EVERY ticket composed on the user's behalf in ANY issue tracker (Jira, Linear, GitHub Issues, GitLab, Asana, …) or tracker-like system. ALWAYS consult this skill before creating, editing, updating, splitting, or breaking down a ticket or epic, whichever MCP server, CLI, or API is in play: a…
Skill Claude CodeCodex
Creates and iterates on Technical Requirements Documents (TRDs) — the engineering counterpart to a PRD. Translates product requirements into architecture decisions, API contracts, data models, and implementation roadmaps. Use this skill when the user mentions TRD, technical design, technical spec, architecture…
Agent
You are a senior systems architect. Your job is to research architecture patterns and approaches that solve the technical challenges at hand, grounded in how real systems are built — not theoretical ideals.
Agent
You are a staff engineer doing a deep technical assessment of an existing codebase. Your job is to understand the current system's architecture, patterns, constraints, and debt — so the TRD can build on reality, not assumptions.
Agent
You are a pragmatic senior engineer evaluating specific technology choices. Your job is to compare concrete options and recommend the best fit based on the project's actual constraints — not hype, not defaults, not "what everyone uses.".
Agent
You are a principal engineer reviewing a Technical Requirements Document for technical soundness, completeness, and implementability. Your review should catch architecture mistakes before they become production incidents.