From tdk-retro
Read retro-feedback.md and propose concrete technical or memory learning deltas. Writes learning-delta.md.
How this skill is triggered — by the user, by Claude, or both
Slash command
/tdk-retro:tdk-retro-proposeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
If prerequisite resolution fails and no local example fixture exists, stop. Do not guess feature paths.
If prerequisite resolution fails and no local example fixture exists, stop. Do not guess feature paths.
Transform collected feedback into up to 10 reviewable learning delta entries. This skill proposes changes only; it does not edit target files.
../_shared/learning-delta-schema.md../_shared/signal-target-routing.md../_shared/consumer-skill-discovery.md../_shared/script-command-contract.mdParse $ARGUMENTS as TASK_ID.
PROJECT_DIR="${CLAUDE_PROJECT_DIR:-${GITHUB_WORKSPACE:-$(git rev-parse --show-toplevel 2>/dev/null)}}"
if [ -z "$PROJECT_DIR" ]; then
echo "Cannot resolve project root. Run from a git workspace or set CLAUDE_PROJECT_DIR/GITHUB_WORKSPACE."
exit 1
fi
(cd "$PROJECT_DIR/.specify/scripts/ts" && bun src/commands/util/check-prerequisites.ts {task_id} --paths-only --json)
Store FEATURE_DIR from the JSON output.
Fixture fallback: if path resolution fails and $PROJECT_DIR/.specify/examples/specs/{TASK_ID}/ exists, use that path as FEATURE_DIR. Do not require plan.md; this skill only requires retro-feedback.md.
Read {FEATURE_DIR}/retro-feedback.md. If missing, stop and ask the user to run /tdk-retro-collect {TASK_ID} first.
When reading ## From: User Feedback, use only entries with status: active; ignore entries with status: removed.
Follow ../_shared/consumer-skill-discovery.md:
.claude/skills/*-ut/SKILL.md
.claude/skills/*-test/SKILL.md
If no consumer test skills exist, do not create T4 entries. Record the no-op in rationale when relevant.
Check:
.specify/memory/memory-index.md
.specify/memory/memory.yaml
If either is missing, ask:
Memory is not initialized. Run /tdk-memory-init before proposing memory entries?
If the user declines or memory remains missing, skip K1/K2 targets and propose only technical targets T1-T6.
For each feedback signal:
../_shared/signal-target-routing.md.memory-index.md.blocked entry that says to run /tdk-memory-init.Write {FEATURE_DIR}/learning-delta.md using ../_shared/learning-delta-schema.md.
Required fields per entry:
Report:
/tdk-retro-apply {TASK_ID}npx claudepluginhub vinhltt/tdk --plugin tdk-retroMines projects and conversations into a searchable memory palace. Activates on queries about MemPalace, memory palace, mining, searching, palace setup, wings, rooms, drawers, or recalling past work.
Guides Payload CMS config (payload.config.ts), collections, fields, hooks, access control, APIs. Debugs validation errors, security, relationships, queries, transactions, hook behavior.
Implements vector databases with Pinecone, Weaviate, Qdrant, Milvus, pgvector for semantic search, RAG, recommendations, and similarity systems. Optimizes embeddings, indexing, and hybrid search.