Add scope-discipline directives to the always-on working-style standard

[assert-not-singularity]

Why

Agents frequently overcomplicate solutions — preserving backward compatibility nothing depends on, generalizing beyond the ask, re-deriving values the input already states, or extending every layer a pattern touches. The always-on working-style.md standard covered honesty and propose-before-acting but had nothing on scope minimalism, while scalable-architecture.md nudges the other way (ports/adapters, boundary validation). This adds the missing always-in-context counterweight.

What changed

All in plugin/templates/standards/working-style.md (the always-on standard, so it applies to every task in every repo that installs preflight):

• Prefer the simplest solution. Don't add backward-compatibility shims, dead code paths, or versioning that nothing depends on. Keep compatibility only where a real consumer relies on it (a versioned/published API, an SLA, a production pipeline, a persisted data format) — and when genuinely unsure, ask instead of defensively keeping both paths.
• Solve the specific ask, not its generalization. No generalized version until a second concrete caller exists — with an explicit carve-out so it doesn't contradict scalable-architecture's single-implementation interfaces for test fakes / swappable I/O boundaries.
• Don't re-derive what the input already states. Read the authoritative value rather than building a parallel second source of truth.
• Name the defect in one sentence, then make that sentence false. Let that sentence bound the fix.
• Justify each touched file against the requirement, not architectural symmetry. Mirror pattern shape, not breadth.

Also:

• Updated the README summary of working-style.
• Bumped the plugin version 0.1.0 → 0.2.0 so /preflight:update surfaces the change to already-scaffolded projects.

Notes

• Kept as a flat bullet list (no new sub-heading) to match the file's existing structure and leanness mandate.
• Deliberately did not touch scalable-architecture.md — the new always-on bullets already supply the counterweight it was missing, and the generalization bullet explicitly defers seam decisions back to that rule where a project follows it.

🤖 Generated with Claude Code

---

Generated by Claude Code

[Copilot]

🟢 Approval recommended

Changes are limited to documentation/standards text plus a straightforward manifest version bump with no apparent behavioral risk.

Pull request overview

This PR updates the always-on working-style standard to add explicit “scope discipline” directives that steer agents toward minimal, non-overgeneralized implementations, and surfaces that update via documentation and a plugin version bump.

Changes:

• Added new working-style bullets covering simplest-solution bias, avoiding premature generalization, not re-deriving stated inputs, bounding fixes with a one-sentence defect, and justifying touched files by requirement.
• Updated the README’s summary line for working-style to reflect the new scope-discipline emphasis.
• Bumped the plugin manifest version from 0.1.0 to 0.2.0 so updates are discoverable via /preflight:update.

File summaries

File	Description
README.md	Updates the working-style row summary to mention scope discipline / simplest-solution guidance.
plugin/templates/standards/working-style.md	Adds new always-on bullets that constrain scope, avoid unnecessary compatibility/generalization, and bound fixes.
plugin/.claude-plugin/plugin.json	Increments plugin version to surface the updated always-on standard to existing installs.

Review details

• Files reviewed: 3/3 changed files
• Comments generated: 0
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.