Help us improve
Share bugs, ideas, or general feedback.
From lore-development
This skill reconciles specs with what was actually built by comparing implementation artifacts (notes, retros, commissions) against specifications. It updates stale specs to reflect reality and generates specs for work that was done without one. Use when specs have drifted, after a feature cycle completes, or when implementation artifacts exist without a corresponding spec. Triggers include "back-propagate", "reconcile specs", "update spec from implementation", "spec drift", "what changed from the spec", "generate spec from notes", "specs out of date".
npx claudepluginhub rjroy/vibe-garden --plugin lore-developmentHow this skill is triggered — by the user, by Claude, or both
Slash command
/lore-development:back-propagateThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Reconcile specifications with reality. Information normally flows forward (spec, plan, implementation). This skill flows it backward: implementation artifacts tell you what was actually built, and the spec gets updated to match.
Analyzes divergences between spec files and code, recommends spec updates or code fixes with reasoning, and executes evolution with user control or auto-updates. Use when mismatches arise in spec-kit workflows.
Transforms ideas into structured specifications (requirements, design, tasks) before implementation. Use when building features, fixing bugs, refactoring, or designing systems.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Share bugs, ideas, or general feedback.
Reconcile specifications with reality. Information normally flows forward (spec, plan, implementation). This skill flows it backward: implementation artifacts tell you what was actually built, and the spec gets updated to match.
/tend when status mode finds specs marked "implemented" that look stale/back-propagate [spec-path] # Reconcile a specific spec against its artifacts
/back-propagate scan # Find specs that may have drifted
/back-propagate generate [topic] # Generate a spec from implementation artifacts
Given a path to a spec (or a topic that resolves to one), compare what the spec says against what happened.
.lore/plans/ for plans referencing this spec (check related: and body text).lore/notes/ for notes whose source: field points to a plan for this spec.lore/retros/ for retros referencing this spec or its plan.lore/commissions/ for commissions whose prompt references this spec or plan.lore/lore-config.md exists, check custom directories toolinked_artifacts for files that were actually changedNot all differences matter. Focus on these:
| Signal | Meaning |
|---|---|
| Requirement fulfilled differently than specified | The "what" stayed, the "how we verify" changed |
| Requirement dropped during implementation | Feature scoped down |
| Requirement added during implementation | Feature grew beyond spec |
| New entry/exit points not in the spec | Integration surface changed |
| Success criteria impossible to verify as written | Criteria were aspirational, not testable |
| Stubs resolved but spec not updated | Connections now exist that the spec calls unknown |
Things that are NOT divergences:
## Divergence Report: [Spec Name]
### Artifacts Reviewed
- Plan: `.lore/plans/feature-x.md`
- Notes: `.lore/notes/feature-x.md`
- Retro: `.lore/retros/feature-x.md`
- Commissions: [N] commission artifacts
### Requirements Drift
| Requirement | Spec Says | Reality | Source |
|-------------|-----------|---------|--------|
| REQ-X-3 | "User sees notification" | Notification was cut for v1 | notes, Divergence section |
| (new) | (not in spec) | Admin dashboard added | commission-Developer-20260305 |
### Entry/Exit Points Changed
| Change | Details | Source |
|--------|---------|--------|
| New entry | REST API added (not in spec) | commission linked_artifacts |
| Exit removed | Webhook integration deferred | retro lessons |
### Stubs Resolved
| Stub | Now Points To |
|------|---------------|
| [STUB: user-auth] | `.lore/specs/auth-flow.md` |
### Success Criteria Status
| Criterion | Status | Notes |
|-----------|--------|-------|
| "User can authenticate" | Met | |
| "Supports SSO providers" | Partially met | Only Google, not all providers |
### Recommended Spec Updates
1. Remove REQ-X-3 or mark as deferred
2. Add REQ-X-8: Admin dashboard view
3. Update exit point table
4. Resolve [STUB: user-auth] to link
After presenting the divergence report:
date: to todayimplemented but divergences were found, suggest status: revisedPreserve the spec's voice and structure. Don't rewrite sections that haven't changed. Add a brief revision note at the bottom:
## Revision History
- YYYY-MM-DD: Back-propagated from implementation. [brief summary of changes]
Find specs that may have drifted without checking a specific one.
.lore/specs/ with status implemented or approvedimplemented but no retro exists: medium (can't verify)## Drift Scan Results
### High Likelihood
| Spec | Signal | Artifacts |
|------|--------|-----------|
| specs/feature-x.md | Notes divergence section non-empty | notes, retro |
| specs/auth-flow.md | Retro mentions dropped requirement | retro |
### Medium Likelihood
| Spec | Signal | Artifacts |
|------|--------|-----------|
| specs/views.md | 6 commissions (heavy iteration) | commissions |
| specs/workers.md | Implemented, no retro | plan, notes |
### No Drift Detected
| Spec | Status |
|------|--------|
| specs/checkout.md | Notes divergence empty, retro clean |
User picks which specs to reconcile. Run Mode 1 on each selected spec.
For work done without a spec. Generates one retroactively from what was built.
source: plan has no corresponding specrelated: link to a spec/specify document structure, but written in past tense where appropriate:
.lore/specs/ after confirmationimplemented (it already is)A retroactive spec describes what exists, not what should exist. Use present tense for current behavior: "The system validates input before processing" not "The system shall validate input."
Don't invent requirements that weren't built. If the code does three things, the spec has three requirements, not five aspirational ones.
Use the lore-researcher agent via Task tool to find related artifacts. Provide the spec name, feature topic, or plan path as the search query. The researcher searches frontmatter fields (title, tags, modules) and body text.
For commissions and meetings (custom directories), search by:
prompt fieldslinked_artifacts for overlap with files the spec's plan would touch/specify creates specs forward (before building)/back-propagate updates specs backward (after building)/retro captures lessons; back-propagate uses those lessons to fix the spec/tend status flags stale specs; back-propagate resolves them/excavate documents existing code; back-propagate documents existing lore artifacts