team-hindsight-dev

Orchestrate a coding session with hindsight-dev-memory-lead plus GitNexus-safe implementation. Use for multi-step C# work, story implementation, or resuming deferred tasks with memory.

Files1

SKILL.md1.4 KB

SKILL.md.claude/skills/team-hindsight-dev/SKILL.md

Team: Hindsight + GitNexus Dev

Coordinates persistent session memory with code-intelligence gates.

When to use

/dev-story on non-trivial stories
Multi-file delegation/sim changes
Resuming work: "continue where we left off"
Post-PR iteration with review memory

Protocol

Read hindsight-gitnexus and hindsight-dev-memory.
Run .\tools\hindsight\Test-HindsightServer.ps1 (non-blocking if down).
Spawn hindsight-dev-memory-lead via Task tool as the primary implementer.

Optional parallel specialists (only if scope requires):

Need	`subagent_type`
C# implementation	`c-sharp-engineer`
Tests	`c-sharp-test-engineer`
Determinism audit	`determinism-engineer`
Post-playtest AAR	`hindsight-aar-analyst`
Trait tuning	`balance-tuning-memory-agent`

Stop conditions

HIGH/CRITICAL gitnexus_impact without user approval
Hindsight down → proceed with GitNexus; note missing memory in report

Deliverables

Code changes (approved paths)
Retain summaries on dev-cmano-clone / dev-story-*
Closing note: banks used, tests run, gitnexus_detect_changes status

Related in other

limits-colimits

Context management for Claude Code. Hooks maintain state via ledgers and handoffs. MCP execution without context polluti...

ddttom-allaboutv2-claude-skills-block-collection-and-party

The Block Collection and Block Party are repositories for existing AEM blocks, build tools, code snippets, integration p...

nodnarbnitram-claude-code-extensions-claude-skills-esphome-confi

This skill should be used when the user asks to "create an esphome config", "set up an esp32 device", "configure esphome...