v2.7.0 — Predict-Before-Reveal

The Junior profile moves from type every line to predict-before-reveal: ownership becomes the ability to evaluate code, not transcribe it.

Highlights

• Predict-before-reveal loop — on each implementation task the junior commits a prediction (approach, data structure, control flow, edge cases) before the AI writes the code, then the AI grades it against a rubric and names the specific gap.
• Inline hard gate — the loop runs as a new /own:feature Phase 6 (Junior profile), so it can't be skipped; only judgment-carrying Implementation tasks gate.
• Prediction Scorecard — per-dimension MATCH/PARTIAL/MISS logged to the global learning registry, turning "is judgment improving?" into a measurable curve.
• Adaptive fading — the gate relaxes per-dimension as the junior proves the skill (4 consecutive matches), with a deterministic staleness re-check so it never decays into a rubber-stamp.
• Self-explanation OWN step — juniors explain why the actual approach is better and where their prediction broke, feeding /own:done Gate 1 with real ownership evidence.
• Evidence-based — design validated against learning-science literature and real-world industry practice (docs/research/junior-profile-predict-before-reveal-validation.md).

See CHANGELOG.md for the full list.

v2.6.0 — Dashboard Elevated

• Added a boot sequence — a terminal window types your live project status (phases, task counts) on load; any key skips it, prefers-reduced-motion bypasses it, #noboot disables it
• Added a command palette (⌘K/Ctrl+K with platform-aware label, or /) for jumping between views; digits 1–9 jump directly and [ ] cycle
• Added a tmux-style status bar with live segments: version, project, active phase, task totals, DoD percent, and a ticking clock
• Added a mission track to the Overview — the roadmap as a timeline with complete, active (pulsing), and roadmap-only nodes; clicking a node navigates to its phase
• Added per-phase task-burn progress bars to the Overview, derived from the same task data the kanban renders
• Added micro-interactions: pointer-tracking tile glow, count-up stats, kanban column progress bars, a segmented Definition-of-Done bar, marching-ants diagram connectors, and aurora/radar-sweep atmosphere
• Fixed the architecture diagram stretching to fill wide tiles and text overflowing its boxes — layout is now content-aware (label gutter and node boxes size to their text via JetBrains Mono's fixed metrics), with clipped text preserved as a hover tooltip
• Fixed Windows PowerShell 5.1 failing to parse the installers when run from disk — all .ps1 scripts are now pure ASCII (the same convention Chocolatey and Scoop installers use)
• Expanded the render test from 35 to 48 assertions and added drift guards: every shipped command must be documented in CLAUDE.md.template, and every .ps1 must stay pure ASCII
• The PR review gate now runs one full review when a PR opens and cheap incremental reviews (previous comments + newly pushed commits only) on each push, with turn caps and a one-comment praise cap
• Existing projects upgrade by replacing dashboard.html only — the window.PROJECT contract is unchanged and dashboard-data.js is untouched

v2.5.0 — The Dashboard SDD Release

The "Dashboard SDD" Release

OwnYourCode's spec-driven development workflow moves from a folder of six Markdown files to a single, live, app-like dashboard you open in your browser.

Highlights

• Six files → one dashboard. Mission, stack, roadmap, and every phase's spec / design / tasks now live in two files: dashboard.html (a stable view shell — layout + styling + render logic) and dashboard-data.js (window.PROJECT, the single source of truth every /own:* command reads and writes).
• A double-click artifact — no server. The shell loads its data via <script src> (which works under the file:// protocol, where fetch() is CORS-blocked), so you open the dashboard straight from disk while still pulling web fonts from the network.
• DASHBOARD_CONTRACT.md ships into every project as the schema authority: field semantics, per-command mutation rules, the phase lifecycle (roadmap-only → specced → complete), and the safety invariants — node --check after every write, exact-string Edit by globally-unique task id, and "the shell is never hand-edited for content."
• Dashboard-native workflow: /own:init fills it from the Q&A flow, /own:feature specs the next roadmap-only phase, /own:done flips tasks by id and completes phases, and /own:status + /own:guide read it (read-only).
• App-like cockpit: header + sidebar + per-phase Spec / Design / Tasks tabs, a hand-rolled SVG architecture diagram (no library — redraws from data), and a kanban board with a live progress ring. Stack rows carry source attribution (package.json / mcp:DATE / verify:URL / manual).
• Default theme — "Terminal-Futurism": a 1:1 capture of ownyourcode.dev — dark near-black surfaces, a terminal-green accent with glow, Outfit + JetBrains Mono, and a signature "ghost numeral" motif. Motion gated by prefers-reduced-motion.
• /own:theme is the styling engine: it regenerates only the dashboard's inline <style> + font <link> — backup-first, with a post-write integrity check that auto-restores if the render contract is damaged, plus a --revert flow. It never touches your data.

Quality

Backed by a 76-test regression suite (install + render + contract) and a manual walkthrough.

---

Full details: see CHANGELOG.md → [2.5.0].

v2.3.0 - The Profiles Release

Different developers learn differently. OwnYourCode now meets them where they are.

Profiles

Profile	Best For
Junior	Learning to code, building software engineer fundamentals
Career Switcher	Transitioning from another field
Interview Prep	Preparing for job interviews
Experienced	Understands software engineering, has experience
Custom	Full personalization

Key Features

• Manifest as single source of truth for all profile settings
• Same 6 Gates quality standards, different teaching approaches
• Conditional blocks in templates activate based on settings

What's New

• Profile selection during /own:init
• /own:profile command to view/change settings
• Free-text background for Experienced profile
• Junior must propose roadmap phases (collaborative design)
• CLI scaffolding uses official tools
• All installation scripts synced (bash + PowerShell)

Installation

# Mac/Linux
curl -sSL https://raw.githubusercontent.com/DanielPodolsky/ownyourcode/main/scripts/base-install.sh | bash

# Windows
irm https://raw.githubusercontent.com/DanielPodolsky/ownyourcode/main/scripts/base-install.ps1 | iex

v2.2.5

What's Changed

Bug Fixes

Version Fetching - Fixed stale version numbers in stack.md for new projects

• Added mcp__octocode__packageSearch to allowed-tools for real-time npm version fetching
• Added explicit version fetching protocol with package names and workflow example
• Prevents Claude from using outdated internal knowledge for versions

Directory Location - Fixed ownyourcode/ being created in wrong location

• Added "CRITICAL: You Are UPDATING, Not Creating" section
• Clarifies that ownyourcode/ already exists from installation (sibling to CLAUDE.md)
• Prevents creating duplicate directories when running own:init from project subdirectories

Files Changed

• .claude/commands/own/init.md - Both fixes applied
• scripts/project-install.sh - Version bump
• scripts/project-install.ps1 - Version bump

Full Changelog: v2.2.4...v2.2.5

v2.2.4 - Clean Install/Uninstall Fix

What's Changed

Bug Fixes

• CLAUDE.md duplication fixed - Install now checks both ./CLAUDE.md and .claude/CLAUDE.md locations, respects existing placement
• Clean uninstall - Fresh installs now fully remove CLAUDE.md on uninstall (no orphan files)
• User skills preserved - Uninstall only removes OwnYourCode skill folders, leaves user custom skills untouched

New Features

• Manifest tracking - .claude/ownyourcode-manifest.json tracks what was installed for surgical uninstall
• Windows uninstall script - Added project-uninstall.ps1 for Windows parity

Improvements

• Default CLAUDE.md location is now project root (Claude Code best practice)
• Dynamic summary shows actual CLAUDE.md location after install

Full Changelog: v2.2.3...v2.2.4

v2.2.3 - Version Accuracy Fix

Fixed

Version Accuracy in /own:init

• Stack recommendations now show verified versions with source attribution
• Existing projects: versions read directly from package.json (source of truth)
• New projects: versions verified via MCP, or show "Verify at [docs URL]" if unavailable
• Added Source column to stack.md template (package.json / MCP verified / Verify at URL)
• Added Version Freshness section to remind users when to re-verify
• Prevents outdated version numbers (e.g., "React 18+") from appearing in generated docs

v2.2.2 - Patch Release

Minor repository maintenance.

Changed

Repository Configuration

• Added .claude/agents/ to .gitignore for personal agent files

---

v2.2.1 - Patch Release

Bug fix for piped installation.

Fixed

Piped Installation Prompt

• Fixed interactive prompt not appearing when running curl ... | bash
• Now reads from /dev/tty instead of stdin to get actual user input

---

v2.2.0 - The Ownership & Polish Release

Focused on clarity, consistency, and Windows compatibility.

Here's what's changed

README Transformation

• Redesigned as a focused landing page (239 → 148 lines)
• Surfaced "The 4 Protocols" as visible methodology
• Removed badge wall and visual clutter
• Changed positioning from "for Juniors" to universal ownership message
• New tagline: "AI guides, you build. You own the result."

Command Naming Unification

• All commands now consistently use /own: prefix
• Improved command descriptions for clearer purpose
• Better onboarding flow in /own:init

Skill Auto-Invocation

• Optimized skill descriptions for improved pattern matching
• Skills now trigger more reliably based on file context

Fixed

Windows Installation

• Fixed PowerShell string escaping (parentheses → brackets)
• Fixed here-string compatibility issues
• Used irm for project-install to bypass git encoding problems
• Windows users can now install without manual intervention

---