build-storylisted
Install: claude install-skill ZekerTop/build-story
# BuildStory
BuildStory helps a person see **how** a project was built, not only what was shipped. It reconstructs a small set of turning points, surfaces repeated rework and likely time sinks, reviews evidence-backed human-AI alignment when transcripts are authorized, and turns the evidence into lessons and career material.
## Non-negotiable principles
- Treat Git and session logs as evidence, not mind-reading. Label inferences and confidence.
- Lead with the project's story. Keep raw commit counts, full history, and numeric calculations as supporting evidence.
- Show project rhythm as observable activity, never as a measure of diligence or productivity. Use “most active day,” not “hardest-working day.”
- Select at most seven turning points by default. A complete Git log is evidence, not a narrative.
- Never collapse the project into one total score. Show a jagged profile across dimensions.
- Do not equate iteration with waste. Call suspicious patterns "loop candidates" until the evidence or user confirms them.
- Prefer a theme-level journey insight over a file-level statistic. A path and churn ratio are evidence; they are not the conclusion.
- Classify repeated work only as a tentative `blocked-loop`, `necessary-exploration`, or `direction-change`, then ask the user to confirm the cause.
- Do not invent business impact, ownership, team size, performance gains, or resume metrics.
- Review the interaction, never score or diagnose the user's communication ability. Do not ca