Agent Skills: manage-product-ideas
Use when the user asks to capture, clarify, document, audit, generate, compare, prioritize, validate, or realize product ideas. Guides one-question-at-a-time discovery, evidence-based scoring, explicit readiness decisions, and scoped delivery without assuming a specific product, repository layout, or planning plugin.
ID: jmerta/codex-skills/manage-product-ideas
13014
Install this agent skill to your local
Skill Files
The files that make up manage-product-ideas.
More agent skills
- game-developerUse when building game systems, implementing Unity/Unreal Engine features, or optimizing game performance. Invoke to implement ECS architecture, configure physics systems and colliders, set up multiplayer networking with lag compensation, optimize frame rates to 60+ FPS targets, develop shaders, or apply game design patterns such as object pooling and state machines. Trigger keywords: Unity, Unreal Engine, game development, ECS architecture, game physics, multiplayer networking, game optimization, shader programming, game AI.
- loop-libraryDiscover, find, compare, audit, repair, adapt, and design repeatable AI-agent loops with explicit triggers, actions, verification, stopping conditions, guardrails, and handoffs. Use when a user asks to analyze a codebase for potential loops, mine coding-thread history for work done more than once, turn repeated engineering work into a loop, find or recommend a published loop, create a recurring agent workflow or automation cadence, turn an outcome into a bounded copy-ready loop, or review an existing loop for weak checks, unsafe authority, unbounded repetition, stale state, or unclear stopping behavior.
- axiom-health-checkUse when the user wants a comprehensive project-wide audit, full health check, or scan across all domains.
- check-rust-coverageCheck which Rust lines are not covered by Rust tests. Use this when you developed new Rust code and want to ensure it is tested.
- factory-triageTriage a Factory work item's issue — trace history, understand architecture, diagnose root cause, then advance the stage
- abridge-core-workflow-aDesign and verify the clinician workflow from consent through recording, draft review, Linked Evidence, and final note disposition. Use when implementing or auditing an Abridge clinical documentation pathway. Trigger with \"map the Abridge note workflow\".