skills.rest
Shockwave2k
Shockwave2kCOMMUNITY
Explore all skills by this author →
GitHub

feature-outcome

Generate feature outcome documents from specs and git diffs, then patch .claude/rules files.

Updated Apr 22, 2026
Search Tags:#automation#git#claude#rules#brain#feature-outcome#outcome.md
One-click install
npx skills add https://github.com/Shockwave2k/team-claude-skills --skill feature-outcome
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feature-outcome
Source: https://github.com/Shockwave2k/team-claude-skills/tree/main/skills/shared/feature-outcome
Command: npx skills add https://github.com/Shockwave2k/team-claude-skills --skill feature-outcome

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When features ship, teams forget what landed and which rules may be stale. This Skill captures shipped changes and updates the project brain to keep Claude's context accurate.

Core Features & Use Cases

  • Ship outcome recording: generates .claude/features/<slug>/outcome.md from the feature spec and git diff.
  • Brain and rules maintenance: patches affected .claude/rules/*.md to surface new APIs, schemas, and connection points.
  • Automation at feature close: runs as Phase 3 of the /feature command or on-demand after a feature lands.

Quick Start

Trigger the /feature workflow to record the final outcome when a feature is complete.

Frequently Asked Questions about feature-outcome

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I record shipped feature changes from a git diff?▼

To record shipped feature changes, generate an outcome document from the feature spec and git diff. This captures the actual landed changes in a markdown file for future reference.

Why does Claude's context become stale after shipping a feature?▼

Claude's context becomes stale because shipped features introduce new APIs and schemas that existing rules files do not reflect. Patching the project brain updates these contracts to keep sessions aligned.

What is the best way to update project rules after a feature ships?▼

The best way to update project rules is patching affected .claude/rules markdown files to surface new APIs and schemas, ensuring the project brain accurately reflects the latest shipped state.

How do I automate outcome documentation when a feature closes?▼

Automate outcome documentation by running the feature-outcome process as Phase 3 of the feature command, or invoke it on-demand after a feature lands to generate the outcome markdown.

Can I generate an outcome document without a completed feature spec?▼

Generating an outcome document relies on comparing the feature spec against the git diff. Without a completed spec, the process cannot accurately identify and record the actual shipped changes.

When should I patch .claude/rules files in my workflow?▼

Patch .claude/rules files when a feature lands and ships new public surfaces, schemas, or connection points. This maintains the project brain and keeps future automation sessions aligned.

Related Skills

Explore More Software Engineering Skills→
cipherstashcipherstash
17

Commit Workflow

Run pre-commit checks and create atomic conventional commits.

Official
Intermediate
putto11262002putto11262002

component-docs

Generate component documentation from git changes using templates.

Community
Basic
stharroldstharrold

workflow-orchestrator

Coordinate workflow phases and load phase-aligned skills for Git development.

Community
Advanced
tsuna44tsuna44

xddp.feedback

Synchronize manually edited project artifacts back into the Change Requirements Specification.

Community
Advanced