Changelog
Changelog
Section titled “Changelog”v0.4.7
Section titled “v0.4.7”July 21, 2026
Switch to npm-based install
Section titled “Switch to npm-based install”The plugin now installs via npm pack @maestria/kimi-code instead of git-based codeload. maestria update kimi-code no longer re-downloads the same version.
v0.4.6
Section titled “v0.4.6”July 21, 2026
Compact agent directives
Section titled “Compact agent directives”Agent directives compressed to cut context usage by ~38% on the orchestrator prompt without removing rules or intent. Shared specialist rules now live once in global rules instead of being repeated per specialist.
v0.4.5
Section titled “v0.4.5”July 14, 2026
Structured assumption tagging
Section titled “Structured assumption tagging”Adventurer and architect outputs now require [verified] or [inferred] tags on every assumption.
Deterministic agents, cognitive hygiene, outcome specs, and more
Section titled “Deterministic agents, cognitive hygiene, outcome specs, and more”Additional methodology improvements including cognitive hygiene checklist, outcome over activity specs, experiment framing, parallel speculation, incidental findings, and first-principles decomposition.
v0.4.4
Section titled “v0.4.4”July 14, 2026
Structured PR descriptions
Section titled “Structured PR descriptions”Pull request descriptions now follow a consistent format with Summary, Changes, Testing, and Breaking Changes sections. Reviews are faster when every PR uses the same structure.
v0.4.3
Section titled “v0.4.3”July 14, 2026
Auto-create feature branch when landing on main
Section titled “Auto-create feature branch when landing on main”The agent no longer asks for confirmation before creating a feature branch when it lands on main.
Work results format streamlined
Section titled “Work results format streamlined”The post-task summary now uses a table-first format. Changes are prefixed
with + (added), ~ (modified), or - (deleted). Breaking changes are
marked with !, and test file changes are annotated with (test).
v0.4.2
Section titled “v0.4.2”July 14, 2026
Structured work results are now mandatory
Section titled “Structured work results are now mandatory”After every task, the agent must produce a ## Changes summary table.
Documentation audit before every commit is also now required.
v0.4.1
Section titled “v0.4.1”July 10, 2026
- Reordered conventional commit prefixes.
refactoris now the default prefix instead offeat.featis reserved for user-facing features only.
v0.4.0
Section titled “v0.4.0”July 10, 2026
Multi-lens review swarm
Section titled “Multi-lens review swarm”The orchestrator can now dispatch parallel reviewers with different focus areas (Security, Architecture, Performance, UX, General). Issues are categorized [fix]/[dismiss]/[escalate].
Autonomous commit protocol
Section titled “Autonomous commit protocol”Commit is fully autonomous - agent reads git log, composes correct conventional commit message, commits without asking. Push is automatic on feature branches, asks only on main/master.
Eliminate questions - autonomous philosophy
Section titled “Eliminate questions - autonomous philosophy”Agents now exhaust data, document assumptions, and proceed instead of asking for permission. Mid-phase questions eliminated across all specialists.
Review methodology improvements
Section titled “Review methodology improvements”- Observation over reasoning - reviewer prioritizes running code over logical argument.
- Review triage pipeline - issues categorized and validated with conservative conflict resolution.
v0.3.5
Section titled “v0.3.5”July 1, 2026
Code intelligence tool preference
Section titled “Code intelligence tool preference”Agents now prefer code intelligence tools (MCP, CLI, or other) before falling back to grep and read when exploring the codebase.
v0.3.1
Section titled “v0.3.1”June 27, 2026
Two new design principles
Section titled “Two new design principles”Agents now check from first principles before adopting existing patterns, and check for existing solutions before building from scratch.
v0.3.0
Section titled “v0.3.0”June 24, 2026
Project workflow configuration (.maestria/)
Section titled “Project workflow configuration (.maestria/)”Ships the .maestria/ project workflow protocol. Projects using maestria’s agent
directives can now define .maestria/workflow.md for custom delegation sequencing
and .maestria/rules.md for project-specific rules. The orchestrator loads these
via @adventurer delegation.
Effort anthropomorphism guard and writing style guidance
Section titled “Effort anthropomorphism guard and writing style guidance”The orchestrator and all specialists now include explicit guardrails against two common failure modes:
- Don’t anthropomorphize effort - A new Critical Rule tells the dispatcher that thinking “that analysis would be too much work” is a category error for a machine that only routes. The same principle is instilled in all specialists via the global agent rules.
v0.2.1
Section titled “v0.2.1”June 24, 2026
Single source of truth for agent directives
Section titled “Single source of truth for agent directives”Agent prompts and global rules now live in one canonical location (packages/core/agent-directives/) and sync automatically to all platform plugins. The scripts/sync-all and scripts/check-sync tools handle the pipeline.
Minor Changes
Section titled “Minor Changes”- Initial release of
@maestria/kimi-code- a declarative, manifest-based plugin that ports the 8 specialist skills from@maestria/opencodev0.3.2 to Kimi Code v0.13.1. - 8 SKILL.md files - orchestrator + 7 specialists using the v0.3.x Skill Prescription pattern
- Manifest-only plugin - no SDK hooks, no build step; the plugin is pure static config (
kimi.plugin.json+skills/+rules/) - Swarm-aware orchestration - the orchestrator routes ≥3 uniform items through Kimi Code’s
AgentSwarmfor parallel fan-out, with the 7-specialist table covering thecoder/explore/plansubagent profiles - Global rules -
rules/AGENTS.mdwith the 7-specialist delegation table, auto-loaded by Kimi Code from~/.kimi-code/AGENTS.md - Install checklist -
INSTALL.mdwith recommended[[hooks]]and[[permission.rules]]config blocks for tool-layer safety enforcement (persona text alone is advisory) - 20 vitest tests - validate manifest schema, frontmatter, rules budget, and persona safety constraints (reviewer no-edit, adventurer read-only Bash)
See ADR-KC-001 for the full design rationale.