Feature Marker
Skill-first run-through feature workflow for Claude, Codex, and Gemini. Use when the user asks to implement a feature through PRD, TechSpec, Tasks, verification, local commit, and branch handoff. The npm package installs skill files only; the LLM skill performs the workflow.
Install
npx skills add Viniciuscarvalho/Feature-marker --skill feature-markergit clone --depth 1 https://github.com/Viniciuscarvalho/Feature-marker.git /tmp/Feature-marker
mkdir -p ~/.claude/skills
cp -r /tmp/Feature-marker/. ~/.claude/skills/feature-markerPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# feature-marker
Use this skill when the user asks to implement, plan, test, or hand off a
feature with Feature Marker.
The normal invocation is a plain LLM prompt:
```text
Use feature-marker to implement <feature-slug>.
```
Run through the feature by default. Do not use an interactive menu, old CLI
workflow commands, checkpoint JSON, or a JavaScript workflow engine. The package
installer only installs this skill.
## Run-Through Procedure
1. Identify the feature slug from the prompt. If the slug is missing, derive a
short kebab-case slug from the feature request.
2. Read repo state: current branch, base branch, git status, project files, and
any existing `tasks/{slug}/prd.md`, `tasks/{slug}/techspec.md`, and
`tasks/{slug}/tasks.md`.
3. Stop before implementation only when:
- the feature request is too ambiguous to produce useful artifacts;
- the checkout has unrelated uncommitted work and the user has not approved
a worktree or cleanup path;
- required verification or project setup is blocked.
4. Use branch-first isolation. If the current branch is `main`, `master`,
`develop`, or `trunk`, create `feature-marker/{slug}` unless the user gave a
branch name. Use a git worktree only when the checkout is dirty or the user
asks for one.
5. Create or reuse artifacts in `tasks/{slug}/` using the bundled templates:
- `templates/prd-template.md` -> `tasks/{slug}/prd.md`
- `templates/techspec-template.md` -> `tasks/{slug}/techspec.md`Details
- Skill name
feature-marker- Repository
- Viniciuscarvalho/Feature-marker
- License
- MIT
- Repo updated
- 28 May 2026
FAQ
What does the Feature Marker skill do?
Skill-first run-through feature workflow for Claude, Codex, and Gemini. Use when the user asks to implement a feature through PRD, TechSpec, Tasks, verification, local commit, and branch handoff. The npm package installs skill files only; the LLM skill performs the workflow.
How do I install the Feature Marker skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add Viniciuscarvalho/Feature-marker --skill feature-marker. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Feature Marker popular?
It lives in Viniciuscarvalho/Feature-marker, which has 11 GitHub stars and 2 forks.
Related skills
Patton Protocol
13vladimirrott/patton-protocol
Coordinate bounded coding-agent missions when independent delegation improves the task.
Webman
12zjkal/webman-skill
Expert skill for the webman framework (a long-lived, in-memory PHP framework based on workerman). Covers routing, controllers, middleware, database/Redis, custom processes, timers, coroutines (v2), plugin development, and guarding against memory leaks and cross-request state pollution under the resident process model. Use when the project has start.php, config/process.php, or support/bootstrap.php, or when the user mentions webman, workerman, 常驻内存 PHP, 协程 PHP, or long-lived/in-memory PHP.
Meeting Scribe
9alphaparkinc/genpark-skill-meeting-scribe
Meeting Scribe — Real-time meeting intelligence agent that transcribes conversations, identifies action items, and generates multi-dimensional summaries for distribution across platforms.
Ironloop
10edouard-claude/ironloop
Verification-first software engineering harness with 5 layers (spec → gen → test → sim → pentest). Use when generating, reviewing, or planning code with AI agents, especially for Rust projects, new feature work, legacy migrations, or any task where code correctness must be guaranteed. Activates on phrases like "build a", "implement", "refactor", "review this code", "migrate from", "add tests for", or when the user describes a coding task with correctness or security requirements.
Openclaw Genpark Inbox Liquidator
9alphaparkinc/openclaw-genpark-inbox-liquidator
OpenClaw GenPark Inbox Liquidator - Zero-inbox NLP action item and Eisenhower matrix triage engine with automated task extraction and reply drafting.
Specmint Core
12ngvoicu/specmint-core
Persistent spec management for AI coding workflows. Use this skill when the user explicitly mentions specs, forging, or structured planning: says "forge", "forge a spec", "write a spec for X", "create a spec", "plan X as a spec", "resume", "what was I working on", "spec list/status/pause/switch/activate", "implement the spec", "implement phase N", "implement all phases", "generate openapi", or exits plan mode (offer to save as a spec). Also trigger when a `.specs/` directory exists at session start. Do NOT trigger on general feature requests, coding tasks, or questions that don't mention specs
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.