From PDLC Pipeline
Consolidation ritual. Reads every feature-level LEARNINGS file produced since the last pass and promotes recurring patterns into project-level DOMAIN-CONSTRAINTS and DECISIONS, and proposes (never auto-commits) updates to skill prompts. Manually invoked, periodically. A human approves every promotion.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pdlc:consolidate-learningsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Per-feature LEARNINGS files are write-only until something promotes their recurring signal to a level future features actually read. That is this skill. You read the LEARNINGS accumulated since the last consolidation pass and promote **patterns** (not one-offs) into project-level context.
Per-feature LEARNINGS files are write-only until something promotes their recurring signal to a level future features actually read. That is this skill. You read the LEARNINGS accumulated since the last consolidation pass and promote patterns (not one-offs) into project-level context.
Scope: Read LEARNINGS files; promote durable patterns into docs/_constraints/ and docs/_decisions/; propose skill-prompt changes as a reviewable artifact. You do NOT autonomously edit skill files, and you do NOT promote a signal seen in only one feature unless it is unambiguously a standing constraint.
Cadence: Manually invoked. A SessionStart nudge hook reminds when ≥5 un-consolidated LEARNINGS exist, but you may be run any time.
/pdlc:consolidate-learnings
No argument — operates across the whole repo's docs/.
chore-consolidate-learnings-{date}. Pull latest.docs/_decisions/.consolidation-log.md (create it if absent). Every docs/*/LEARNINGS-*.md with a Date Completed after the last logged pass is in scope.docs/_constraints/DOMAIN-CONSTRAINTS.md (read by pm-author).docs/_decisions/DECISIONS-{topic}.md (read by se-author)..consolidation-log.md: date, which LEARNINGS files were consumed, what was promoted, what was deferred.When a learning says a skill prompt itself should change, you do not edit the skill. Write docs/_decisions/CONSOLIDATION-PROPOSAL-{date}.md:
# Consolidation Proposal — {date}
| Source LEARNINGS | Target skill | Proposed change | Rationale |
|---|---|---|---|
| {features} | pdlc/skills/{skill}/SKILL.md | {concrete edit} | {why, and the pattern that motivates it} |
A human reviews and applies (or rejects) each row. This is deliberate: agents proposing changes to the prompts that govern agents must pass through human judgment.
docs/_constraints/DOMAIN-CONSTRAINTS.md entries:
## DC-{NN}: {Constraint title}
**Constraint:** {what must hold for all future features in this domain}
**Origin:** promoted {date} from LEARNINGS of {features}
**Applies to:** {REQ authoring / TSPEC / testing / all}
docs/_decisions/DECISIONS-{topic}.md reuses the per-feature DECISIONS format (DEC-{topic}-{NN}), with an Origin line citing the source features.
.consolidation-log.md updated with date, consumed files, promoted + deferred itemsnpx claudepluginhub ohenak/yumo-plugins --plugin pdlcProvides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.