ferueda
- 26 skills
- 0 followers
- last month last updated
- ▌ Create Plan 2 · ferueda bundleCreate 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.
- ▌ Review Spec 2 · feruedaReview a spec document against codebase reality, identifying gaps and ensuring sound, robust implementations.
- ▌ Handoff Work 2 · feruedaHand 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.
- ▌ Diagnose Issue 2 · ferueda bundleResearch 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.
- ▌ Code Quality Review 2 · feruedaReview 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.
- ▌ Review Implementation 2 · feruedaReview 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.
- ▌ Grove · feruedaUse 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.
- ▌ Audit · ferueda bundleSurvey 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.
- ▌ Cursor CLI · ferueda bundleRun 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`.
- ▌ Interrogator · feruedaInterview 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.
- ▌ Ask Questions · feruedaClarify requirements before implementing. Do not use automatically, only when invoked explicitly.
- ▌ Implement Plan · feruedaExecute 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.
- ▌ React To Review · feruedaEvaluate, 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.
- ▌ Triage · ferueda bundleTriage 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.
- ▌ Architect · ferueda bundleDesign a repository-grounded solution and explain material tradeoffs. Use only when explicitly invoked as architect; return an inline memo, not an implementation plan.
- ▌ Create Plan · ferueda bundleWrite 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.
- ▌ Review Spec · ferueda bundleReview an implementation plan read-only for consequential execution risks and accepted requirements. Not template enforcement, stylistic critique, code-diff review, or automatic plan edits.
- ▌ Handoff Work · ferueda bundleTransfer work context to another agent or session when continuation or review needs it. Return an inline handoff unless an artifact is requested.
- ▌ Diagnose Issue · ferueda bundleInvestigate 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.
- ▌ Explain Change · ferueda bundleExplain 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.
- ▌ Planning Workflow · ferueda bundleRoute work when the next action is unclear or coordination is explicitly requested. Clear implementation tasks do not need this skill or a plan.
- ▌ Adversarial Review · ferueda bundleChallenge a proposed design before implementation planning. Use for design stress tests, not executable plans, code diffs, open-ended ideation, or visual polish reviews.
- ▌ Shape Requirements · ferueda bundleClarify material requirements that block useful progress, or interview a user to develop a brief. Not for routine implementation choices or ordinary document edits.
- ▌ Code Quality Review · ferueda bundleReview substantial structural or abstraction changes read-only for consequential maintainability risks. Not routine polish, a second correctness pass, or surrounding-code cleanup.
- ▌ Review Implementation · ferueda bundleReview 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.
- ▌ Change Review Workflow · ferueda bundleSelect proportionate diff review and coordinate authorized corrections. Choose implementation, quality, both, or skip low-risk work; not an automatic post-edit gate.