Menu
SkillsMP has collected 31 skills from shinpr/codex-workflows. Open a skill to review its source and details.
Showing 31 of 31 collected skills.
Proposes and, after user confirmation, creates or maintains docs/project-context/quality.yaml from repository-specific review requirements. Use when asked to generate or update a repository quality profile.
Execute an approved backend Work Plan autonomously through task execution, quality fixes, commits, and final verification.
Execute an approved frontend Work Plan autonomously through frontend implementation, quality fixes, commits, and final verification.
Reviews completed frontend implementation for governing-source compliance, scope economy, repository quality, and security, and applies user-approved React corrections.
Execute an approved fullstack Work Plan autonomously with layer-aware task routing, quality fixes, commits, and final verification.
Run the full-cycle implementation workflow for one outcome spanning backend and frontend layers.
Orchestrate the complete implementation lifecycle from requirements through verified repository implementation.
Reviews completed implementation for governing-source compliance, scope economy, repository quality, and security, and applies user-approved corrections.
Guides subagent coordination through implementation workflows. Use when: orchestrating multiple agents, managing workflow phases, determining autonomous execution mode, or coordinating recipe execution.
Update existing design documents (Design Doc / PRD / ADR) with review and consistency verification.
Root-cause discipline, proportionate impact analysis, and implementation completeness assurance. Use when fixing bugs, reviewing code quality, refactoring, making technical decisions, or performing quality assurance.
Determines which PRD, ADR, UI Spec, Design Doc, and Work Plan a change requires and where each document lives. Use when deciding documentation scope or creating or reviewing one of these artifacts.
Selects the smallest sufficient implementation strategy and verification boundary from current requirements and repository evidence.
Clarifies inputs, outputs, success criteria, decisions, and unresolved conditions so downstream agents can execute without guessing. Use when writing or revising LLM-facing prompts, handoffs, planning artifacts, reviews, reports, or generated instructions.
Execute from codebase-scoped analysis to design document creation.
Execute from codebase-scoped analysis to frontend design document creation including UI Spec.
Converges future-state requirements around outcome, exclusions, and rough cost. Use when users ask 'do we need this?', 'how far should we go?', or request a feature or scope change.
Analyzes standalone task essence, task type, applicable skills, and metacognitive execution risks.
Create frontend work plan from design document with test skeleton generation.
Creates a reviewed Work Plan with value-filtered integration/E2E test skeletons. Use when planning implementation from a Design Doc.
Generate PRD and Design Docs from existing codebase through discovery, generation, verification, and review.
Evaluates received review results before they generate work by separating problems from proposed fixes and comparing responses in a fixed decision order. Use whenever review results may lead to artifact changes; does not produce reviews.
Investigate problem, verify findings, and derive solutions through structured diagnosis.
Repository-aware implementation rules for minimal design surface, contract safety, representative patterns, and verifiable changes. Use when implementing, refactoring, or reviewing code.
Resolves and records one external evidence source required by a current design or verification decision. Use when repository and supplied evidence cannot determine that decision.
Selects and specifies only integration/E2E tests whose observable boundary cannot be proven more cheaply.
Add integration/E2E tests to existing codebase using Design Docs.
Adjust an implemented UI with focused evidence, verification, and quality checks.
Prepare repository-local execution tools when the user requests setup or a concrete build capability is unavailable.
Repository-aware test execution rules for TDD, observable proof, and boundary selection. Use when writing, reviewing, or fixing tests.
Execute standalone tasks with metacognitive analysis and applicable skill selection.