CtrlK
BlogDocsLog inGet started
Tessl Logo

gitnexus-plan

Use when you need a deep, implementation-ready engineering plan for a code change — built from GitNexus graph intelligence, statement-level PDG analysis, and targeted source verification, compact enough that an implementation agent can start without re-investigating. Also strengthens existing plans via Deepen mode. Examples: "/gitnexus-plan Add retry support to the ingestion pipeline", "/gitnexus-plan deepen docs/plans/<plan>.md", "plan this change using the knowledge graph".

73

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable multi-phase planning workflow with explicit validation checkpoints, feedback loops, and a clean one-level-deep reference architecture. Minor conciseness tightening is possible around repeated provenance contract phrasing.

DimensionReasoningScore

Conciseness

Dense and mostly efficient — it assumes Claude's competence and does not explain basic concepts — but the provenance/writer contract language recurs across Hard rules, Phase 4, Phase 5, and Deepen with some repetition that could be tightened.

4 / 5

Actionability

Fully executable guidance with concrete commands throughout ('node .gitnexus/run.cjs analyze ...', 'query {search_query, task_context}', helper invocations with exact flags like 'write-plan --replace --expected-plan-digest <...>'), concrete path conventions, and a category-budget table covering common cases.

5 / 5

Workflow Clarity

Phases 0–5 are clearly sequenced with explicit validation checkpoints ('Verify before asserting', provenance recompute 'immediately before composition', safe-write failure blocks publication) and feedback loops (stale index → refresh → re-validate; graph/source disagreement → trust source, record, recommend re-index).

5 / 5

Progressive Disclosure

SKILL.md is a concise overview pointing to one-level-deep references (context-ledger.md, pdg-slice.md, plan-template.md, context-pack.md, evidence-provenance.md) and one script (evidence-provenance.mjs), all verified to exist, with clearly signaled navigation.

5 / 5

Total

19

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description with explicit 'Use when...' guidance and concrete command examples that establish a distinct niche. The only deduction is the second-person voice ('you need'), which the rubric penalizes on specificity.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions ('statement-level PDG analysis', 'targeted source verification', 'strengthens existing plans via Deepen mode') with comprehensive coverage, but the second-person phrasing 'Use when you need' incurs the rubric's -1 voice penalty from a 5.

4 / 5

Completeness

Clearly answers both what ('implementation-ready engineering plan... built from GitNexus graph intelligence, statement-level PDG analysis, and targeted source verification') and when via an explicit 'Use when you need...' clause with concrete trigger examples.

5 / 5

Trigger Term Quality

Good natural keyword coverage ('engineering plan for a code change', 'plan', 'deepen', 'knowledge graph') reinforced by three concrete invocation examples, with a few synonyms a user might naturally say still missing.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (GitNexus graph + statement-level PDG + Deepen mode) with distinct triggers and minimal overlap with other skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
abhigyanpatwari/GitNexus
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.