agentleFS
marcowuethrichmarcowuethrich/green-print/.claude/skills/feature-workflow/SKILL.md

feature-workflow

Skill1 starsChanged 17 days agoMITView on GitHub

Takes one GitHub issue of this repository from spec to a merged pull request - worktree, spec, plan, subagents, the every-surface walk, the zero-findings gate, a fresh review, the pull request and the cleanup after the merge. Use when asked to build, implement or ship an issue or a feature here.

11 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the issue and the docs AGENTS.md routes it to.

    line 13
  2. Very specific:

    Test first where the behaviour is clear: a ViewModel test in shared, a Compose UI test in composeApp/src/commonTest, a resource test in …

    line 38
  3. Very specific:

    Run what changed the way a user would (desktop: ./gradlew :composeApp:run, web: ./gradlew :composeApp:wasmJsBrowserDevelopmentRun, Android …

    line 44
  4. Distinctive:

    Remove the worktree and the branch (git worktree remove, git branch -D, the remote branch).

    line 60

“Common” is measured: kept by at least 6 in 10 of the 9 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

Feature workflow

The repository's way to land a change. Every step names its evidence; a step without evidence is not done.

1. Start from the issue

  • Read the issue and the docs AGENTS.md routes it to. Unclear scope: ask now with the question tool, with a recommendation, never later in prose.
  • One worktree per issue, never main: git worktree add .agents/worktrees/<n>-<slug> -b feat/<n>-<slug> origin/main.

2. Spec first

  • A change a user sees gets its spec in docs/features/<name>.md: user stories, flows, edge cases, the reverse states (how to undo or leave it), what is out of scope.
  • An architectural choice gets an ADR in docs/architecture/decisions.md, in the same pull request.

3. Plan, then delegate

  • Split the work into tasks that each stand alone: the shared model and repository, the server endpoint, the UI, the tests.
  • A task with a clear spec goes to a subagent with the whole brief (it sees nothing else): the issue, the worktree path, the files it owns, the rules from AGENTS.md it must keep, what to return. Choose its model and effort as docs/agentic/README.md (Subagents) says.
  • The lead keeps the integration, the questions and the pull request.

4. Build with the project's skills

  • kotlin-project-feature-implementation for placing the code, kotlin-data-kmp-data-layer for repositories and sync, kotlin-ui-compose-multiplatform for the UI, kotlin-testing-kmp for the tests.
  • Test first where the behaviour is clear: a ViewModel test in shared, a Compose UI test in composeApp/src/commonTest, a resource test in server.

5. Prove it

  • Walk Hit every surface in AGENTS.md and write down which entries applied.
  • Run what changed the way a user would (desktop: ./gradlew :composeApp:run, web: ./gradlew :composeApp:wasmJsBrowserDevelopmentRun, Android or iOS on a simulator) and keep a screenshot for the pull request.
  • ./gradlew prePRcheck once, clean. A finding gets fixed, never baselined.

6. Review and pull request

  • A fresh reviewer that did not write the code reads the diff (kotlin-kmp-code-review), with the code, not the author's conclusions. Fix what holds up.
  • Open the pull request with the template: Closes #<n>, the surfaces, the evidence, the gate.
  • Watch the checks; fix a failure in the same branch. Merge when every check is green and every thread is resolved, never with --admin.

7. Clean up

  • Fast-forward the main checkout to origin/main.
  • Remove the worktree and the branch (git worktree remove, git branch -D, the remote branch).
  • File what stayed open as a new issue, so nothing lives only in a chat.

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.