Add user confirmation before skill creation #8
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Reduce SKILL.md from ~3,500 words to ~1,800 words (~48% reduction) - Extract detailed research workflow to resources/research-workflow.md - Extract quality gates, anti-patterns, lifecycle to resources/quality-guidelines.md - Use tables for compact information presentation - Add clear references to existing examples/ directory - Follows Claude Code skill development best practices for progressive disclosure The refactored structure loads core instructions immediately while deferring detailed reference material until needed, reducing context window usage. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Add "User Confirmation Required" section making explicit approval mandatory - Update extraction process: Step 5 now requests user confirmation - Update Retrospective Mode to include "Confirm" step before extraction - Update description to clarify skill always asks before creating - Bump version to 4.1.0 Users now maintain full control over their skill library - no skills are created without explicit approval. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Adds mandatory user confirmation before creating any skill, giving users full control over their skill library.
Builds on PR #7 (token efficiency refactor)
Changes
SKILL.md Updates
New "User Confirmation Required" section - Makes explicit that skills are never created without approval
Step 5: Request User Confirmation - Before saving, must present:
Retrospective Mode - Now includes "Confirm" step before extraction
Updated description - Metadata now states "Always asks for user confirmation"
Version bump - 4.0.0 → 4.1.0
Rationale
The original design triggered skill extraction automatically after certain tasks. This could lead to:
With this change, users decide what gets saved. The skill still identifies candidates and does the work of structuring them, but the final decision is always the user's.
Test plan
/claudeceptionretrospective asks which candidates to create🤖 Generated with Claude Code