all publishers

ferueda

@ferueda source repo

26 published skills

  1. ▌
    Create Plan 2 · ferueda bundle
    Create a scoped, code-backed implementation plan from a todo, spec, issue, review notes, or raw user instructions. Use when the user asks to convert requirements into a proper plan, phased implementation plan, executor handoff plan, or reviewable planning artifact before coding.
    4 installs
  2. ▌
    Review Spec 2 · ferueda
    Review a spec document against codebase reality, identifying gaps and ensuring sound, robust implementations.
    4 installs
  3. ▌
    Handoff Work 2 · ferueda
    Hand off work in progress or finished to another agent for continuation or review. Produce a structured summary with enough background context, what was worked on, how, why, files touched, and what remains. Trigger when the user says "hand off this work", "prepare a handoff", "document what was done for the next agent", or ending a session another agent should pick up.
    2 installs
  4. ▌
    Diagnose Issue 2 · ferueda bundle
    Research and define codebase issues before implementation planning. Use when the user provides an issue statement, bug report, Jira ticket, vague problem, proposed solution, runtime symptom, or design concern and wants Codex to inspect the current codebase, validate whether the problem exists, diagnose likely causes, compare solution directions, and produce an evidence-backed problem definition. Do not use when the user asks for a step-by-step implementation plan, direct implementation, or code review of an existing diff.
    4 installs
  5. ▌
    Code Quality Review 2 · ferueda
    Review recently modified code for clarity, consistency, and maintainability while preserving exact functionality. Audit adherence to project conventions and industry best practices. Trigger when the user wants a code quality review, readability audit, maintainability review, or behavior-preserving refinement suggestions on a diff or implementation.
    6 installs
  6. ▌
    Review Implementation 2 · ferueda
    Review a given implementation critically and adversarially against its plan or spec. Look for antipatterns, red flags, bugs, unnecessary complexity, plan drift, and missing tests. Trigger when the user says "review this implementation", "review these changes", "review this branch", "adversarial review", "challenge these changes", or wants code scrutinized before merging.
    0 installs
  7. ▌
    Grove · ferueda
    Use Grove's lease-first git worktree pool CLI for durable branch-aware worktree leases: acquire, inspect, list, release, repair, destroy, and status. Use when agents or automation need isolated reusable checkouts without cloning repeatedly.
    4 installs
  8. ▌
    Audit · ferueda bundle
    Survey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute. Strictly read-only on source code — never implements, fixes, or refactors anything itself. Use when asked to audit a codebase, find improvement opportunities (bugs, security, performance, test coverage, tech debt, migrations, DX), suggest features or where to take the project next (roadmap, product direction), or generate handoff plans for another agent to implement.
    3 installs
  9. ▌
    Cursor CLI · ferueda bundle
    Run Cursor Agent headlessly and delegate work to another Cursor agent over the CLI. Use when the user asks to call, ask, invoke, run, or delegate to Cursor (e.g. "call cursor", "ask cursor", "invoke cursor agent"); when automating Cursor from scripts or agent-to-agent flows; or when the user mentions `agent -p`, headless Cursor CLI, or `cursor-agent.mjs`.
    5 installs
  10. ▌
    Interrogator · ferueda
    Interview the user to extract knowledge from their head and synthesize it into a structured document. Use this skill when the user wants help thinking through an idea, designing a feature, specifying a task, or articulating something they haven't written down yet. Trigger when the user says things like "interview me about", "ask me questions about", "help me think through", "I need to spec out", "I have an idea for", "let's flesh out", or any variation where they want to be interrogated rather than do the writing themselves. Also use when the user has a vague concept and needs help turning it into a concrete artifact (spec, design doc, brief, plan, etc.) through conversation.
    14 installs
  11. ▌
    Ask Questions · ferueda
    Clarify requirements before implementing. Do not use automatically, only when invoked explicitly.
    0 installs
  12. ▌
    Implement Plan · ferueda
    Execute an approved plan or spec document phase-by-phase, writing robust idiomatic code that follows codebase patterns. Trigger when the user says "implement this plan", "execute the spec", "work through the phases", or a plan in `dev/plans/` is approved and ready for implementation.
    4 installs
  13. ▌
    React To Review · ferueda
    Evaluate, analyze, and systematically react to an adversarial code review report. Decide on the action for each finding (Implement, Adapt, Decline), provide clear justifications, and define the plan to implement the accepted changes.
    3 installs
  14. ▌
    Triage · ferueda bundle
    Triage an issue or work item read-only against repository evidence. Use when asked to assess scope, readiness, duplicates, blockers, or the next agent action; not for routing work already assigned for execution.
    4 installs
  15. ▌
    Architect · ferueda bundle
    Design a repository-grounded solution and explain material tradeoffs. Use only when explicitly invoked as architect; return an inline memo, not an implementation plan.
    4 installs
  16. ▌
    Create Plan · ferueda bundle
    Write a plan when explicitly requested or when safe execution needs durable sequencing, cutover, risk controls, or an executor handoff. File count alone does not justify planning.
    0 installs
  17. ▌
    Review Spec · ferueda bundle
    Review an implementation plan read-only for consequential execution risks and accepted requirements. Not template enforcement, stylistic critique, code-diff review, or automatic plan edits.
    2 installs
  18. ▌
    Handoff Work · ferueda bundle
    Transfer work context to another agent or session when continuation or review needs it. Return an inline handoff unless an artifact is requested.
    0 installs
  19. ▌
    Diagnose Issue · ferueda bundle
    Investigate uncertain code behavior and its cause when diagnosis is requested or needed before choosing a fix. Not for reviewing a diff or writing an implementation plan.
    5 installs
  20. ▌
    Explain Change · ferueda bundle
    Explain a diff, branch, commit range, or pull request through its behavior and tradeoffs. Use for walkthroughs and impact questions, not defect-finding or merge approval.
    4 installs
  21. ▌
    Planning Workflow · ferueda bundle
    Route work when the next action is unclear or coordination is explicitly requested. Clear implementation tasks do not need this skill or a plan.
    5 installs
  22. ▌
    Adversarial Review · ferueda bundle
    Challenge a proposed design before implementation planning. Use for design stress tests, not executable plans, code diffs, open-ended ideation, or visual polish reviews.
    1 install
  23. ▌
    Shape Requirements · ferueda bundle
    Clarify material requirements that block useful progress, or interview a user to develop a brief. Not for routine implementation choices or ordinary document edits.
    2 installs
  24. ▌
    Code Quality Review · ferueda bundle
    Review substantial structural or abstraction changes read-only for consequential maintainability risks. Not routine polish, a second correctness pass, or surrounding-code cleanup.
    4 installs
  25. ▌
    Review Implementation · ferueda bundle
    Review a diff read-only for material correctness and accepted requirements. Use for requested reviews or selected behavioral risk, not routine post-edit checks or automatic fixes.
    2 installs
  26. ▌
    Change Review Workflow · ferueda bundle
    Select proportionate diff review and coordinate authorized corrections. Choose implementation, quality, both, or skip low-risk work; not an automatic post-edit gate.
    2 installs