Feature workflow

Skill YoniChechik/claude-code-config/skills/feature-workflow

End-to-end feature development pipeline: plan → implement → build tests → post checks → PR → summary. Invoked by /new-feature and /continue-feature. this skill should not be invoked directly but rether by the other skills.From its SKILL.md

Install

npx -y skills add YoniChechik/claude-code-config --skill feature-workflow

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

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
0 stars0 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

1.3 KB, 236 tokens by cl100k_base, as published. Nobody here has run it

Feature Development Workflow

The workflow for developing a feature end to end — planning, implementation, testing, and post-implementation tasks.

Each time the user asks to plan, run all stages afterwards.
Each time the user requests a code change/debug, run all stages after implementation.

Process

Step 1: Plan

Run /plan $FEATURE_DESCRIPTION skill.

Step 2: Implement

Use a subagent to write code (opus high effort)
If problems occur, use /debug skill to fix them
After each significant change, commit and push (main agent does this directly)

Step 3: Build Tests

Run /build-tests skill for test planning and building.

Step 4: Post

Run /post skill for quality checks, code review, test review, and lint/format.

Step 5: PR Creation

Run /pr-create skill to create a pull request. This also launches the CI watcher in the background automatically.

Step 6: Summary

Report a summary of what the feature is, how we implemented it, and what happened at all post-implementation steps.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most automation workflows skills give in 236 tokens

Counted across 745 of the 1,008 authors here whose files we hold, read 2026-08-07

Write conventional commit messagesin 36 of 745, across 35 files
Delete branches after mergein 30 of 745, across 21 files
Make atomic commitsin 25 of 745, across 15 files
Write minimal code to pass testsin 22 of 745, across 10 files
Re-snapshot after navigation or DOM changesin 21 of 745, across 13 files
Use try-catch for error handlingin 20 of 745, across 8 files
Run tests before committingin 20 of 745, across 12 files
Write tests before implementationin 20 of 745, across 8 files
Configure branch protection rulesin 19 of 745, across 5 files
Explain the why in commit messagesin 19 of 745, across 9 files
Refactor code while tests remain greenin 19 of 745, across 6 files
Interact with elements using refsin 19 of 745, across 11 files

Said here and by no other author read

run plan skill first
use subagent to write code
use debug skill to fix problems
run build-tests skill for test planning
run post skill for quality checks
run pr-create skill to create pull request

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.