Documents completed feature with summary of what was built, key decisions, files changed, and lessons learned. Updates roadmap. Use after manual testing verification passes.
/plugin marketplace add astrosteveo/harness/plugin install harness@astrosteveo-marketplaceThis skill is limited to using the following tools:
You are helping a developer document a completed feature and close out the development session.
Progress is saved to .artifacts/{feature-slug}/ for session continuity.
Document what was accomplished and update the roadmap.
Feature context: $ARGUMENTS
progress.md to mark all phases completesummary.md.artifacts/roadmap.md:
Create summary.md:
# {Feature Name} - Summary
## Completed
{Date completed}
## What Was Built
{Description of the feature}
## Key Decisions
| Decision | Rationale |
|----------|-----------|
| {decision} | {why} |
## Files Modified
| File | Changes |
|------|---------|
| `{path}` | {summary of changes} |
## Files Created
| File | Purpose |
|------|---------|
| `{path}` | {purpose} |
## Manual Testing
- Tested by: {User}
- Date: {date}
- Result: PASSED
- {Summary of what was verified}
## Known Limitations
- {Any limitations or technical debt}
## Future Improvements
- {Potential enhancements}
## Lessons Learned
- {What went well}
- {What could be improved}
Update progress.md:
## Status
Phase: COMPLETE
Started: {date}
Completed: {date}
## Current State
- [x] Phase 1: Discovery
- [x] Phase 2: Codebase Exploration
- [x] Phase 3: Clarifying Questions
- [x] Phase 4: Architecture Design
- [x] Phase 5: Implementation
- [x] Phase 6: Quality Review
- [x] Phase 7: Manual Testing Verification
- [x] Phase 8: Summary
docs({feature-slug}): complete feature summarydocs(roadmap): mark {feature-slug} complete, add deferred itemsCongratulate the user on completing the feature. Provide a brief summary of the journey:
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.