v1.8.7

v1.8.7

Release Date: 2026-03-27

Eject Command, Statusline Enhancements, and Leaner Skills

Adds a destructive eject command to fully decouple projects from the update mechanism, enriches the statusline with cost and usage tracking, and removes generic build/test skills in favour of per-project generation.

What's New

• Eject command (/5:eject): Permanently removes all update infrastructure (hooks, version tracking, update command) from a project, giving teams full ownership of workflow files without ongoing update checks
• Statusline branch display: Current git branch is now shown in the status line for quick orientation
• Statusline cost and usage tracking: Running session cost, 5-hour usage percentage, and the next usage-reset time are now displayed in the status line
• Off-peak rocket indicator: A rocket indicator appears in the status line during off-peak API hours

Improvements

• Removed generic build and run-tests skills: build-project and run-tests are no longer shipped as generic skills — they are generated per-project during /5:configure, tailored to the actual build system and test runner in use
• Consolidated configure documentation: Configure-related reference material reduced from 7 files to 3, cutting noise and making the configure flow easier to follow

Affected files:

• src/commands/5/eject.md (new)
• src/hooks/statusline.js (modified)
• src/skills/build-project/SKILL.md (removed)
• src/skills/run-tests/SKILL.md (removed)
• src/commands/5/configure.md (modified)
• src/commands/5/reconfigure.md (modified)
• src/skills/configure-project/SKILL.md (modified)
• bin/install.js (modified)
• README.md (modified)

---

1.8.6

v1.8.6

Release Date: 2026-03-23

Phase Boundary Enforcement and CLAUDE.md Workflow Rules

Strengthens guardrails that prevent plan-feature from leaking into implementation planning, and adds persistent workflow rules to the generated CLAUDE.md.

Bug Fixes

• Plan-feature phase containment: Added explicit constraints in the plan-feature command against creating implementation plans, offering to continue into Phase 2, or suggesting next phases — prevents the LLM from jumping into Phase 2 territory mid-command
• Plan-guard file whitelist: During Phase 1 (plan-feature), only .planning-active, codebase-scan.md, and feature.md are writable; attempts to create plan.md or other implementation artifacts are blocked

Improvements

• Workflow rules in CLAUDE.md: Configure and reconfigure now include a "Workflow Rules" section in the generated CLAUDE.md, instructing the LLM to follow /5: command instructions exactly, not skip steps or combine phases, and only create artifacts belonging to the current phase — provides persistent context-level reinforcement against phase breakout

Affected files:

• src/commands/5/plan-feature.md (modified)
• src/hooks/plan-guard.js (modified)
• src/commands/5/configure.md (modified)
• src/skills/configure-project/SKILL.md (modified)

1.8.5

Release Date: 2026-03-23

Scoped Rules Generation

Adds support for generating .claude/rules/ files during configuration — scoped instruction files that automatically load when Claude works with matching file types.

What's New

• Rules generation: Configure and reconfigure now offer to generate .claude/rules/ files with project-specific conventions derived from codebase analysis
• File-type scoping: Rules use paths: frontmatter so they only load when editing relevant files (e.g., testing rules for test files, API rules for controller files)
• Four rule categories: code-style.md, testing.md, api-patterns.md, and dependencies.md — each generated only when matching patterns are detected

Improvements

• Reconfigure rules support: Reconfigure detects existing rules, identifies stale ones, and offers to create/refresh/remove as needed
• Config schema updated: Added rules.generate field to .5/config.json
• Concise directives: Rules are 15-40 lines of actionable directives, not documentation — documentation stays in .5/*.md files

Affected files:

• src/commands/5/configure.md (modified)
• src/commands/5/reconfigure.md (modified)
• src/skills/configure-project/SKILL.md (modified)
• src/references/configure-tables.md (modified)

1.8.4

Explore Caching, Deep Work Enforcement, and Implementation Reliability

Reduces redundant codebase scans across phases, strengthens planning guardrails, and adds regression detection and dependency verification to implementation.

What's New

• Explore caching: Phase 1 now saves codebase scan results to codebase-scan.md. Phase 2 reuses the cache instead of re-scanning, saving significant tokens and time
• Decision propagation: Feature specs now tag Q&A answers as [DECIDED], [FLEXIBLE], or [DEFERRED]. Phase 2 honors decided items exactly, exercises discretion on flexible ones, and excludes deferred items from the plan
• Pattern File & Verify columns: Plan table expanded from 6 to 8 columns — each component now specifies an existing file to read before implementing and a concrete verification command
• Regression baseline: Phase 3 runs build/tests before implementation starts, then classifies post-implementation failures as regressions vs. pre-existing
• Pre-step dependency check: Before executing each step, the orchestrator verifies prior steps' output files still exist on disk, preventing cascading failures
• Quick-implement scope gate: Blocks tasks that exceed 5 files or 3 modules, redirecting to the full workflow

Improvements

• Context budget rules: Orchestrator now follows strict rules to keep context lean — never reads source files directly, discards full agent output after parsing RESULT blocks
• Bash blocked in planning: Plan-guard hook now intercepts file-writing Bash commands (cat >, echo >, sed -i, etc.) that would bypass Write/Edit guards
• Stronger role checks: Added ROLE CHECK callouts at each planning step to prevent premature implementation
• Escalating block messages: Plan-guard now references the specific planning phase and directs back to the Progress Checklist on repeated violations
• Executor improvements: Component executor now reads pattern files before writing code, runs verify commands after implementation, reports deviations, and has a 3-attempt auto-fix limit
• Progress checklists: Re-added to planning commands for step tracking

v1.8.3

Remove disable-model-invocation from All Commands

Removes the disable-model-invocation: true frontmatter property from all 12 workflow commands, allowing model invocation during command execution.

Affected files:

• All 12 command files in src/commands/5/

v1.8.2

Orphaned File Cleanup

Automatically removes files from previous versions that are no longer part of the package, keeping user projects clean after updates.

Improvements

• File manifest tracking: Fresh installs and updates now save a manifest of installed files in .5/version.json, enabling precise orphan detection on future updates
• Manifest-based cleanup: On update, diffs the old manifest against the current one and deletes files/directories that are no longer managed
• Legacy upgrade support: For upgrades from versions without a manifest, a static list of 8 known removed agent files is cleaned up automatically
• Thorough uninstall: Uninstall now also removes legacy orphaned files, not just currently managed ones

Affected files:

• bin/install.js (modified)

1.8.1

Streamlined Planning Commands

Inlines agent content directly into planning commands, improves plan-implementation with better test tier guidance and config awareness, and removes task tracking overhead from the planning phases.

Improvements

• Inlined planning agents: Removed separate feature-planner.md and implementation-planner.md agent files — their content is now embedded directly in plan-feature and plan-implementation commands, reducing indirection and improving maintainability
• Deferred ticket extraction: plan-feature no longer prompts for ticket confirmation — it silently extracts the ticket ID from the git branch when writing the spec, keeping the Q&A flow uninterrupted
• Three-tier test planning: plan-implementation now detects and plans for unit, integration, and e2e tests based on what frameworks the explore agent finds in the project, instead of only planning unit tests
• Config-aware planning: plan-implementation reads .5/config.json for build/test commands and project type, passing them to the explore agent and using them in the Verification section
• Plans-as-prompts guidance: Added explicit documentation that plan.md is interpolated into agent prompts — descriptions should be action-oriented instructions, not passive documentation
• Complexity rubric: Added structured rubric with decision heuristic for assigning simple/moderate/complex to components
• Plan template updated: PLAN.md template now includes spec frontmatter field, testing strategy section, and integration/e2e test rows
• Removed task tracking: Planning phases no longer use Task-based progress tracking, reducing overhead

Affected files:

• src/agents/feature-planner.md (removed)
• src/agents/implementation-planner.md (removed)
• src/commands/5/plan-feature.md (modified)
• src/commands/5/plan-implementation.md (modified)
• src/templates/workflow/PLAN.md (modified)
• bin/install.js (modified)

v1.8.0

Skill-Creator Plugin, Command Guardrails, and Token Optimization

Integrates the skill-creator plugin for higher-quality project skill generation, adds structured role blocks to all commands for stronger behavioral guardrails, and significantly reduces token usage through redundancy removal and reference extraction.

What's New

• Skill-creator plugin support: /5:configure and /5:reconfigure now detect the skill-creator MCP plugin (create-skill/scaffold-skill tools), offer one-command installation if not present, and record availability in config.json under tools.skillCreator.available. When available, the configure-project skill uses its tools instead of template-based generation for higher-quality output
• References directory: Large static content (detection tables, config schema) extracted from configure.md into src/references/configure-tables.md, loaded at runtime via context frontmatter — keeps command files focused on logic
• Explicit model declarations: All commands now declare their intended model (opus, sonnet, or haiku) in frontmatter, making model selection explicit rather than implicit

Improvements

• Role constraint blocks (<role> tags with identity, scope, and behavioral rules) added to all commands that lacked them: configure, discuss-feature, implement-feature, quick-implement, reconfigure, update, verify-implementation. Planning commands (plan-feature, plan-implementation) received expanded role blocks with additional inline constraints
• Removed redundant Instructions Summary sections from implement-feature and quick-implement
• Consolidated 4 repeated MANDATORY VERIFICATION blocks into single-rule shorthand markers
• Removed Example Workflow sections from plan-feature, plan-implementation, discuss-feature
• Removed TaskCreate 8-task checklist overhead from plan-feature
• Trimmed duplicate constraint expressions (DO NOT lists, repeated no-code rules, question templates) across planning commands
• Net token reduction of ~170 lines across commands while preserving all functionality
• bin/install.js updated to handle references/ directory in managed files and selective updates
• Frontmatter field ordering standardized across all commands

1.7.2

Release Date: 2026-03-02

Block EnterPlanMode During Workflow Planning Phases

Prevents Claude Code's built-in EnterPlanMode tool from being invoked during the 5-phase workflow's planning commands, eliminating interference between the built-in plan mode and the workflow's own structured planning process.

Bug Fixes

• plan-guard.js hook now intercepts and blocks EnterPlanMode calls when a planning phase is active, returning a clear redirect message instructing the agent to continue with its workflow artifact instead
• Escalating warning messages are surfaced after repeated blocked attempts (3+ blocks), matching the existing escalation behavior for other blocked tools
• feature-planner and implementation-planner agent instructions now include an explicit constraint (NEVER call EnterPlanMode) as a first-line defense before the hook fires
• settings.json hook matcher updated from Task|Write|Edit to Task|Write|Edit|EnterPlanMode so the plan-guard.js hook is triggered for the new tool

Affected files:

• src/hooks/plan-guard.js (modified)
• src/agents/feature-planner.md (modified)
• src/agents/implementation-planner.md (modified)
• src/settings.json (modified)

v1.7.1

Version Tracking Cleanup and Update Cache Isolation

Cleans up the internal version.json schema and moves the update availability cache to a separate gitignored file, eliminating noisy git diffs caused by the check-updates hook writing to a tracked file.

Improvements

• latestAvailableVersion is now stored in .5/.update-cache.json (gitignored) instead of version.json, so the check-updates hook no longer causes uncommitted changes in users' repos
• Removed the redundant installedVersion field from version.json; packageVersion is now the single source of truth for the installed version
• ensureDotFiveGitignore() function added to bin/install.js to create and maintain .5/.gitignore on fresh install and upgrade, automatically adding .update-cache.json to it
• performUpdate() now reconstructs version.json from known fields only, automatically pruning legacy or stale properties from older installs
• check-updates.js and statusline.js hooks updated to read/write latestAvailableVersion from the new cache file