Ship Go Features with TDD: skillshare-implement-feature

Where this fits

You ask your agent to add a new --json flag to your Go CLI. Without guardrails, it jumps straight into production code, leaves no tests, and wires the flag through a handler that ignores your project's split conventions. This skill solves that by making test-first development and project-specific patterns the default for every feature request.

Why agents benefit

• It turns a vague request into a concrete sequence: read the spec, extract acceptance criteria, identify affected packages, write failing tests, implement, and verify.
• It bakes in your repo's conventions — handler split, oplog instrumentation, and dual-mode global/project patterns — so agent code matches existing style.
• It explicitly scopes the work to Go code and tests, preventing drift into docs or changelog edits mid-task.
• It accepts a spec file path or a plain-text description, so agents can start from specs/my-feature.md or from a chat message.
• It makes TDD deterministic: the agent cannot treat tests as optional because the workflow demands them first.

Practical scenarios

Adding a new CLI command

When you ask for skillshare serve, the agent reads specs/add-serve.md, writes a failing test for the new handler, then implements the command with the required split and instrumentation. You get a reviewable diff with test coverage attached.

Creating an internal package

A request like "build a rate limiter package" is passed as a plain description. The skill extracts edge cases, creates table-driven tests first, and only then writes the package using the repo's established patterns.

Adding a flag to an existing command

The agent identifies the command handler from the spec, writes a test for the new flag's behavior, updates the handler, and confirms the dual-mode global/project behavior still passes.

Add it to your agent workflow

Add the skill with:

npx skills add runkids/skillshare --skill skillshare-implement-feature

Then invoke it by pointing at a spec file or describing the feature:

Use skillshare-implement-feature with specs/add-retry-flag.md

The agent follows the TDD workflow and stops before docs or changelog updates, so you can run those separately with dedicated skills.

Compare before adopting

Before adding it, compare a few things. Quality signals: does the repo have clear tests, recent commits, and passing CI? Maintenance freshness: check if the skill is updated for your agent runtime, not just popular. Alternatives: a generic TDD prompt may work, but it won't enforce your project's split and instrumentation conventions. Workflow fit: this skill is Go-specific and expects skillshare-style patterns; if your codebase differs, plan to adapt the conventions.

Why it is worth tracking

This skill is worth tracking because it hard-codes a workflow and project conventions into agent behavior, which is more useful than a generic prompt. The 2.6k-star repo signals strong community demand for deterministic TDD agent skills. Bookmark its OpenAgentSkill listing at https://www.openagentskill.com/skills/runkids-skillshare-implement-feature to monitor updates and compare it with similar Go workflow skills. Re-evaluate when your project conventions change or when you start doing more feature-implementation cycles.