/skills/using-humane

Next move

Read the current artifact and handoffs to choose the next Humane skill for the work that actually exists.

What is the next unresolved decision?

Learn

A narrow job with a visible boundary

Use it when several skills could help, the cycle has been entered midway, or a review leaves multiple possible next steps.

Input

The current artifact, known evidence, unresolved findings, and the skills available in the environment.

Outputs

  • A named next skill and reason
  • Required inputs before running it
  • A clear stop when no Humane skill is appropriate

Boundary

The router follows evidence and handoffs. It does not force every project through every skill or invent work to keep the cycle moving.

Invocation

humane:using-humane

See the decision change

The prototype is accepted but visual roles are still ad hoc. Run design-tokens before implementation; review follows once the interface is operable.

The next move follows the current unresolved dependency.

1 / 2
  1. Too many options

    Should we run tokens, review, or before-after next?

    The prototype is accepted but visual roles are still ad hoc. Run design-tokens before implementation; review follows once the interface is operable.

  2. No useful handoff

    Add another Humane step after approval.

    No additional Humane skill is required. Ship the approved work and collect real usage evidence for the next cycle.

Run the skill by name

Install the Humane pack once, then name this skill when the task reaches its boundary.

humane:using-humane