Full Changelog: v0.2.12-public...v0.2.13-public

Full Changelog: v0.2.11-public...v0.2.12-public

Highlights

• publish the current project engineering strategy package as the latest public release
• add prototype-based visual acceptance requirements for UI and page work
• align acceptance terminology around acceptance methods and the acceptance main entry
• keep internal, public-skill, and public repository exports synchronized

Included since v0.2.5-public

• formalized documentation taxonomy
• tightened remote tracker and tracker-schema mutation gates
• surfaced remote-tracker approval earlier in the workflow
• formalized test-document acceptance entry layout
• aligned acceptance-entry terminology

Highlights

• add a soft related-skill reminder rule to project-engineering-strategy
• check whether a clearly related skill is actually available in the current session before relying on its workflow
• first reminder target is brainstorming for design-first work such as scoping, requirements clarification, and solution comparison
• keep the reminder non-blocking: suggest installation once, then continue with best-effort execution if the user does not install it

Coordination

• document the reminder scope in SKILL_COORDINATION.md
• avoid turning the strategy into a generic "install more skills" prompt

Highlights

• add formal rules for syncing docs/superpowers/ and .superpowers/brainstorm/ output into the project's official doc root
• treat the official doc root as the default user review source, not the working-layer planning artifacts
• prevent treating unreviewed working-layer docs as confirmed formal design or plan baselines
• require same-round formal-doc sync before reporting official conclusions, preparing acceptance artifacts, or committing/pushing

Packaging

• keep the public skill package generic by removing local repository-specific CodexProject wording from the published reference copy

Public docs update synced to current main.

Highlights:

• added a hard rule for critical, evidence-based strategy advice
• requires strategy discussion and recommendations to stay grounded in facts, constraints, evidence, and explicit assumptions
• prevents agreement-seeking or user-led rationalization from overriding technical judgment

Public docs update synced to current main.

Highlights:

• added social preview assets to the public repo
• clarified Chinese-readable title and terminology rules for stable engineering docs
• formalized Hum Check handling so self-tested work is not prematurely marked Done

Public packaging refresh focused on discovery and trust.\n\nHighlights:\n- rewrote the root README as a clearer landing page\n- added MIT license\n- added CONTRIBUTING, CODE_OF_CONDUCT, issue templates, and PR template\n- improved repository metadata for search and community use

Initial public release of the project-engineering-strategy skill.\n\nHighlights:\n- cross-session engineering workflow baseline\n- acceptance and self-test governance rules\n- tracker, execution contract, and local-doc coordination model\n- clean public package layout for Codex installation