agentleFS
Sign inStart free
phoenixvnphoenixvn/claude-code-agency/.claude/skills/implement/SKILL.md

implement

Skill0 starsChanged 7 months agoMITView on GitHub

Full development pipeline from feature definition to tested code. USER APPROVAL GATE Agents work within their domain directories: - Frontend: src/frontend/ - Backend: src/backend/ - Shared types: src/shared/ Present review results. Update sprint progress in active.md.

191 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use setup-ts-deep-modules, ask-matt and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • liufeng1976Skill

    setup-ts-deep-modules

    Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.

    Also in 43 projects that use this

  • GoogleSkill

    ask-matt

    Ask which skill or flow fits your situation. A router over the skills in this repo.

    Also in 91 projects that use this

  • RoentekSkill

    loop-me

    Grill me about specs for the workflows I want to build, within this workspace.

    Also in 50 projects that use this

  • AWSSkill

    to-questionnaire

    Turn a decision you can't fully answer into a questionnaire for someone else to fill in.

    Also in 88 projects that use this

  • ryotaroh180105Skill

    claude-handoff

    Hand the current conversation off to a fresh background agent that picks up the work immediately.

    Also in 42 projects that use this

  • GoogleSkill

    to-spec

    Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.

    Also in 168 projects that use this

  • +3 more from google

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 171 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write test cases from acceptance criteria

    line 44

“Common” is measured: kept by at least 6 in 10 of the 171 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/implement — Feature Implementation

Full development pipeline from feature definition to tested code.

Instructions

Phase 1: Feature Definition

Use AskUserQuestion:

  • "What feature should we implement?" (free text)
  • "Is there a design spec or wireframe?" → read if yes
  • "What are the acceptance criteria?" (free text)

Phase 2: Task Breakdown

Spawn dev-lead to:

  • Break the feature into implementation tasks
  • Identify frontend vs backend vs database work
  • Estimate complexity (S/M/L) per task
  • Identify dependencies and ordering
  • Present task list for approval

USER APPROVAL GATE

Phase 3: Implementation (parallel where possible)

Based on task breakdown, spawn relevant agents:

  • frontend-developer — UI components, pages, client-side logic
  • backend-developer — API endpoints, services, business logic
  • database-engineer — Schema changes, migrations, seed data (if needed)

Agents work within their domain directories:

  • Frontend: src/frontend/
  • Backend: src/backend/
  • Shared types: src/shared/

Phase 4: Integration

Wire frontend to backend:

  • API client setup
  • Type sharing
  • Error handling
  • Loading states

Phase 5: Testing

Spawn qa-tester to:

  • Write test cases from acceptance criteria
  • Execute tests
  • Report any failures

Phase 6: Code Review

Spawn dev-lead to review all new code for:

  • Quality, readability, maintainability
  • Security (input validation, XSS, injection)
  • Performance (unnecessary re-renders, N+1 queries)
  • Accessibility (semantic HTML, ARIA)

Present review results. Update sprint progress in active.md.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free