PolarionMcpServers: Command for Claude Code

.claude/commands/incremental-implementation.md

incremental-implementation is a command for Claude Code from peakflames/PolarionMcpServers. It costs 0 tokens per session (5,140 once invoked), scanned A, original, MIT.

A step-by-step workflow for implementing features in the PolarionMcpServers project in small, testable batches. It includes checking project state, validating changes with MCP tools, and waiting for approval before pushing or merging.

In plain words
What is it for?
Use it to inspect branches and plans, identify incomplete work, implement one phase at a time, test it, and prepare changes for user-approved commits, pushes, or merges.
Why use it?
It prevents unfinished work and unreviewed repository changes from being mixed into a feature implementation.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions CLAUDE.md.

This is peakflames/PolarionMcpServers's own configuration. It tells Claude Code how to work on PolarionMcpServers itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything PolarionMcpServers configures →

Reuse

Borrowing it

Nothing to install: this file belongs to peakflames/PolarionMcpServers. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/peakflames/PolarionMcpServers/main/.claude/commands/incremental-implementation.md
Clone the repo
git clone --depth 1 https://github.com/peakflames/PolarionMcpServers

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for incremental-implementation

README.md
[![agentmods](https://agentmods.dev/badge/commands/peakflames/polarionmcpservers/incremental-implementation/github.svg)](https://agentmods.dev/commands/peakflames/polarionmcpservers/incremental-implementation)
Your own site
<a href="https://agentmods.dev/commands/peakflames/polarionmcpservers/incremental-implementation"><img src="https://agentmods.dev/badge/commands/peakflames/polarionmcpservers/incremental-implementation/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for incremental-implementation

Your own site · 80×15
<a href="https://agentmods.dev/commands/peakflames/polarionmcpservers/incremental-implementation"><img src="https://agentmods.dev/badge/commands/peakflames/polarionmcpservers/incremental-implementation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 5,140 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.05140
Opus 5.5 $0.00000 $0.02056
Sonnet 5.5 $0.00000 $0.01028
Haiku 4.5 $0.00000 $0.00514

Measured 2mo ago against content hash bf41c84a6234, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

incremental-implementation scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/commands/incremental-implementation.md · 823 lines

How it starts

The opening of the file, as written. The whole thing — 823 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Incremental Phase Implementation Workflow


No Task Specified Protocol

<no_task_protocol> When the user does not specify a task (e.g., empty message, "continue", "what's next?"), Claude must proactively assess the project state and propose next steps.

Step 1: Assess Current State

  1. Check Git Status

    git status && git branch -a && git --no-pager log --oneline -10
    
  2. Identify Current Phase and Version

    • Read CHANGELOG.md for current version
    • Check recent commits for current work context
  3. Check for Existing Implementation Plans

    • Look for docs/plans/ or tmp/ for implementation plans
    • Identify current task status
  4. Check for Incomplete Work

    • Review any verification checklists in docs/verification/
    • Check for uncommitted changes or unmerged feature branches

Step 2: Determine Next Action

Based on the assessment, recommend ONE of the following:

State Recommended Action
Uncommitted changes exist Complete current work, commit, await approval
Feature branch exists but not merged Complete task, await approval for merge
Phase plan exists with incomplete tasks Propose starting next task
Current phase complete, no next phase plan Propose creating next phase implementation plan
All phases complete Propose maintenance, enhancements, or new phase planning

Step 3: Present Proposal to User

Format the proposal clearly:

## Project State Assessment

**Current Version:** {version}
**Current Branch:** {branch}
**Last Commit:** {hash} - {message}

## Recommendation

{One of the following:}

**Option A: Continue Current Work**
- Task: {task description}
- Status: {status}
- Next Steps: {specific steps}

**Option B: Start New Task**
- Phase {N} Task {M}: {title}
- Dependencies: {met/unmet}
- Estimated effort: {S/M/L}

**Option C: Create Phase {N+1} Implementation Plan**
- Current phase status: Complete
- Suggested next phase focus: {area}
- Would you like me to draft the implementation plan?

Read the full file on GitHub · 823 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2mo ago First seen · 823 lines · 0 tokens per session scan A bf41c84a6234

Subscribe to this mod's changes

incremental-implementation is a command published in the GitHub repository peakflames/PolarionMcpServers (43 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 5,140 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

incremental-implementation compared with commands from other repositories

incremental-implementation next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
incremental-implementationpeakflames/PolarionMcpServersCommand437d agoMITA0Claude Code
checklistgithub/spec-kitCommand148kyesterdayMITA13Claude Code
clarifygithub/spec-kitCommand148kyesterdayMITA27Claude Code
specifygithub/spec-kitCommand148kyesterdayMITA13Claude Code
analyzegithub/spec-kitCommand148kyesterdayMITA26Claude Code
convergegithub/spec-kitCommand148kyesterdayMITA35Claude Code
implementgithub/spec-kitCommand148kyesterdayMITA14Claude Code