new-feature

Post-launch setup for a new feature worktree — detect context, recall memories, and transition to brainstorming.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

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

The body is highly actionable with a clear, well-guarded workflow, but it is verbose in spots through duplication and does not use progressive disclosure — everything lives inline in one ~80-line file.

Suggestions

Remove the duplicate 'Don't guess from the branch name' guidance — keep only the bold callout in step 4.

Trim the 'Important' section to points not already established in the Preamble/Steps to reduce redundancy.

If this skill grows, offload the phase-handoff pipeline details into a referenced file so the body stays an overview with one-level-deep references.

Dimension	Reasoning	Score
Conciseness	The body is largely lean with concrete commands and no basic-concept padding, but 'Don't guess from the branch name' is stated twice (step 4 prose and its bold callout) and the 'Important' section rehashes points already covered, so it could be tightened below a 3.	2 / 3
Actionability	Provides exact, copy-paste-ready commands (git/mark_chapter payload/printf) plus a literal output template and the named pipeline, meeting the fully-executable anchor at 3 rather than the pseudocode anchor at 2.	3 / 3
Workflow Clarity	A clearly numbered preamble + 6-step sequence with explicit guards ('If the current branch is main or master... tell the user to create a worktree first') and confirmation checkpoints ('ask BEFORE recalling more', 'ask for confirmation'), satisfying the explicit-checkpoint anchor at 3.	3 / 3
Progressive Disclosure	The content is well-sectioned into a single file with no nested references, but at ~80 lines with no bundle files it is monolithic rather than an overview pointing one level deep to detail files, so it lands at the 'some structure' anchor rather than 3.	2 / 3
	Total	10 / 12 Passed

Description

67%

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

The description is specific and action-oriented with a clear niche, but it lacks an explicit 'Use when...' trigger clause, which weakens both trigger guidance and the when-should-use completeness.

Suggestions

Add an explicit trigger clause, e.g. 'Use when launched inside a freshly created feature worktree before any feature work begins.'

Include natural user-facing variations such as 'new feature', 'feature branch', 'start a feature' alongside 'worktree' to broaden trigger coverage.

Keep the third-person imperative voice already in use; just append the when-condition rather than restating the actions.

Dimension	Reasoning	Score
Specificity	Lists three concrete actions — 'detect context, recall memories, and transition to brainstorming' — matching the multi-action anchor rather than the single-domain anchor at 2.	3 / 3
Completeness	The 'what' is explicit, but the 'when' is only implied by 'Post-launch setup for a new feature worktree' with no explicit trigger clause, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Terms like 'new feature worktree' and 'brainstorming' are reasonably natural, but there is no 'Use when...' clause and common variations are missing, so it does not reach full keyword coverage at 3.	2 / 3
Distinctiveness Conflict Risk	'Post-launch setup for a new feature worktree' plus 'transition to brainstorming' carves a clear niche unlikely to fire for unrelated skills, satisfying the distinct-trigger anchor at 3.	3 / 3
	Total	10 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: AndreJorgeLopes/devflow
Commit: 9556c94

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.