agentsclimarketplace

Implement

Skill shikanime-labs/skills/skills/workflow/implement

A curated catalog of self-improved agent skills for Hermes and compatible agents

Install
npx -y skills add shikanime-labs/skills --skill implement

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.8 KB, as published. Nobody here has run it

Implement

Load the context for a task. This skill prepares the ground: the feature was validated as an issue by to-spec / to-tickets; now you gather and present the context so the user can implement it.

Read docs/agents/domain.md for vocabulary and respect the ADRs in the area you touch. Fetch the originating issue per docs/agents/issue-tracker.md.

Process

  1. Understand the task. Read the spec/ticket thoroughly. Identify:

    • The problem statement and solution approach
    • User stories and acceptance criteria
    • Implementation decisions and technical constraints
    • Affected modules and their interfaces

  2. Explore the codebase surface. Map the territory:

    • Read the files the change touches
    • Trace the real flow end to end
    • Identify existing patterns, helpers, and utilities
    • Note test seams and property frameworks in use
    • Check for sibling call sites (for bug fixes)

  3. Present the context. Summarize what you found:

    • Task objective and acceptance criteria
    • Files and modules involved
    • Existing patterns to reuse
    • Test strategy and seams
    • Minimalism considerations (see docs/agents/workflow.md)

  4. Wait for user direction. The user is in control of implementation. Present the context clearly, then wait. Do not implement unless explicitly directed.

Minimalism discipline (reference)

The minimalism discipline is always on (see docs/agents/workflow.md for the canonical ladder): stop at the first rung that holds — (1) does this need to exist? (YAGNI) → skip; (2) already in this codebase? → reuse; (3) stdlib does it? → use it; (4) native platform feature? → use it; (5) installed dependency? → use it; (6) one line? → one line; (7) only then the minimum that works.

Never cut validation, error handling, security, or accessibility.

Bug fixes (context-loading mode)

A ticket names a symptom. Before presenting context, find every caller of the affected function and present the root cause location where all callers route through — one guard in the shared function, not one in every caller. Note the regression test strategy.

Boundaries

Loads context for one spec/ticket. Sized to a single context window — if it doesn't fit, it should have been split by to-tickets. Does not implement unless explicitly directed by the user. Does not self-merge or land the stack.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.