Feature Request
Add a new refactor skill to the Han plugin suite.
What's known
The request is to add a refactor skill. No further detail on scope or behavior has been supplied yet.
Open questions (to resolve before specifying)
- Job to be done: What does an operator hand
/refactor, what does it produce, and what does it change?
- Distinction from existing skills: How does it differ from refactoring already covered by the refactor step in
/tdd, /code-review, and /architectural-analysis?
- Success criteria: What does a good run of
/refactor look like?
- Code vs. artifact: Does the skill write code (like
/tdd) or produce a plan/report (like the analysis skills)? Which plugin does it belong in (han.core or elsewhere)?
- Triggers: When would an operator reach for
/refactor over an existing skill?
Suspected area
han.core/skills/ — where Han's skills are defined.
Recommended next step
Clarify the job-to-be-done and how it differs from existing skills before specifying. Once the use case is settled, /plan-a-feature (or /research if the build-vs-reuse question stays open) is the natural follow-up.
Triaged with /issue-triage.
Feature Request
Add a new
refactorskill to the Han plugin suite.What's known
The request is to add a
refactorskill. No further detail on scope or behavior has been supplied yet.Open questions (to resolve before specifying)
/refactor, what does it produce, and what does it change?/tdd,/code-review, and/architectural-analysis?/refactorlook like?/tdd) or produce a plan/report (like the analysis skills)? Which plugin does it belong in (han.coreor elsewhere)?/refactorover an existing skill?Suspected area
han.core/skills/— where Han's skills are defined.Recommended next step
Clarify the job-to-be-done and how it differs from existing skills before specifying. Once the use case is settled,
/plan-a-feature(or/researchif the build-vs-reuse question stays open) is the natural follow-up.Triaged with
/issue-triage.