ferueda/harness
Reusable engineering skills for planning, diagnosis, review, and handoff.
Challenge a proposed design before implementation planning. Use for design stress tests, not executable plans, code diffs, open-ended ideation, or visual polish reviews.
Design a repository-grounded solution and explain material tradeoffs. Use only when explicitly invoked as architect; return an inline memo, not an implementation plan.
Select proportionate diff review and coordinate authorized corrections. Choose implementation, quality, both, or skip low-risk work; not an automatic post-edit gate.
Review substantial structural or abstraction changes read-only for consequential maintainability risks. Not routine polish, a second correctness pass, or surrounding-code cleanup.
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.
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.
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.
Transfer work context to another agent or session when continuation or review needs it. Return an inline handoff unless an artifact is requested.
Route work when the next action is unclear or coordination is explicitly requested. Clear implementation tasks do not need this skill or a plan.
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.
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.
Clarify material requirements that block useful progress, or interview a user to develop a brief. Not for routine implementation choices or ordinary document edits.
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.