Results for “developer-prompt”

10 skills

theheavenlyd3mon

Use when asked to fix, build, refactor, review, verify, or release software and the work is non-trivial — including delivering a change request (issue, ticket, or request) from intake through planning, gates, implementation, review, verified PR, and authorized post-merge release. neckbeard routes the change through framing, discovery, design, implementation, review, verification, delivery, and learning — choosing the smallest *safe* intervention, proving it at the real delivery boundary, and leaving an inspectable evidence ledger. For change-request / issue-to-PR work, conditionally loads a 9-phase journey with gates, delivery packet, and lifecycle integration. Composes specialist catalog skills rather than replacing them. Not a persona, not a '10x developer' prompt, not a LOC-minimizer. The journey is not loaded for plain fixes, refactors, or reviews that lack an issue/ticket trajectory.

More results

gtm-developer-ecosystem

Build and scale developer-led adoption through ecosystem programs, community, and partnerships, focusing on what drives adoption.

Runs focused experiments to validate feasibility of an idea, saving artifacts to .planning/spikes/ and supporting both idea and frontier modes.

Generate Product Requirements Documents through structured conversation for any project. Use when starting a new feature, documenting requirements, creating specs before implementation, or needing clarity on scope and success criteria.

leandrobenjaminl

Formaliza una idea como propuesta de cambio antes de invertir tiempo en especificaciones y diseño, alineando contexto, alternativas, impacto y criterios de éxito.

Use when driving a feature prompt to a production-ready PR through discovery, definition, design, spec, issues, and dev phases, or when the user runs /feature or /feature resume — orchestrates the A-Team agentic pipeline over a target repo.

Turn a generic product tour into a buyer-specific demo that only shows what they told you hurts. Maps every feature you plan to show to a problem the buyer actually stated, writes the "so what" for each moment, and flags the trap of feature-dumping before you fall into it. Built for B2B sales teams, customizable to your product and your discovery. Trigger on "build a demo script", "prep for the demo", "what should I show", "map features to pain", "stop me from feature dumping", or any pre-demo planning pass.

Run a structured discovery interview and produce a complete, developer-ready Product Requirements Document. Load when the user asks to write a PRD, create product requirements, document a feature, define user stories with acceptance criteria, or turn a rough idea into a formal product requirements document. Also triggers on "document this feature", "write requirements for", "create a one-pager", "turn this into a PRD", "I need a PRD for", or any request to produce a structured product document for stakeholder alignment or engineering handoff. Supports Full PRD, Lean PRD, and One-Pager formats. Note: for executable feature specifications (FRs, NFRs, ACs as Given/When/Then consumable by AI coding agents), route to `feature-spec` instead — PRDs frame the product, feature-specs encode the implementable contract.

product-management

Trigger: PM, product tasks, project planning, backlog priority, user stories, ticket scoping. Scope: Product management, task priorities, requirements scoping. Boundary: Excludes writing raw code or designing page layouts.

expert-software

软件开发团队专家团入口。用于 Codex CLI 的 $expert-software 调用。支持快速模式、BugFix、标准 SOP、PRD、架构设计、代码实现、测试验证。触发词：软件开发、写代码、修 bug、PRD、架构设计、测试、QA、工程交付