Add KISS Principle semantic anchor

[Copilot]

Adds the KISS (Keep It Simple, Stupid / Keep It Super Simple) semantic anchor to the catalog — a foundational design principle in software development that was missing from the collection.

New anchor files

• docs/anchors/kiss-principle.adoc — English anchor with core concepts (simplicity as design goal, avoid over-engineering, readability over cleverness, progressive enhancement), proponents (Kelly Johnson, Robert C. Martin), tier 1
• docs/anchors/kiss-principle.de.adoc — German translation

Updated

• YAGNI (.adoc + .de.adoc + anchors.json) — added kiss-principle as a related simplicity anchor; the two principles are closely complementary
• skill/semantic-anchor-translator/references/catalog.md — added KISS entry so agent tooling can discover and suggest it
• website/public/data/anchors.json — manually maintained JSON updated and then regenerated via extract-metadata.js (107 anchors total, up from 106)

Anchor metadata

:categories: design-principles
:roles: software-developer, software-architect, consultant, educator
:proponents: Kelly Johnson, Robert C. Martin
:related: yagni, dry-principle, solid-principles
:tags: kiss, simplicity, design-principles, over-engineering, readability
:tier: 1

Both interpretations of the acronym are acknowledged ("Stupid" / "Super Simple"), with the description noting the latter as the softer, developer-preferred variant.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[Anchor Proposal]: KISS</issue_title>
<issue_description>### Proposed Term

KISS

Context (Optional)

In Software development context, KISS or KISS principle use to be translated as "Keep It Simple, Stupid", but this can sound rude or unpolite and many devs, including myself, tend to think about kiss principle as Keep It Super Simple. In other words: the goal is make it work, we can improve the solution later on.

Pre-submission Checklist

• I have searched existing anchors and this term is not already included
• This term refers to a well-established concept (not something I invented)</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes [Anchor Proposal]: KISS #352

---

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.

[raifdmueller]

Analysis of Proposed Anchors

Evaluated against the quality criteria: Precise, Rich, Consistent, Attributable.

Summary

PR	Anchor	Tier	Recommendation	Rationale
#354	P.A.R.A. Method	3	⚠️ Discuss	Rich and attributable (Tiago Forte), but knowledge management — not SE methodology. Extends catalog scope.
#355	PERT	2	✅ Accept	Classic estimation technique (1958), precise formula, well-established. Tier 2 is correct — useful but niche.
#356	Spec-Driven Development	3	⚠️ Discuss	Relevant to our workflow doc, but is it an established anchor or an emerging practice? Proponents listed (Swagger, Thoughtworks) are not the originators of the term.
#357	Explicit Contract Surface	3	❌ Reject	Not an established term — it's a combination of existing patterns (ACL, DTOs, contract-first). Proponents listed (Evans, Martin, Fowler) didn't coin this term. Fails "Attributable" criterion.
#358	Vertical Slice Architecture	3	✅ Accept	Well-established (Jimmy Bogard), precise, rich. Tier 3 is justified — complements Clean/Hexagonal Architecture.
#359	GRASP	3	✅ Accept	Classic OO patterns (Craig Larman), 9 well-defined patterns. Tier 3 justified — foundational, widely taught.
#360	KISS	1	⚠️ Discuss	Tier 1 is correctly assigned by Copilot! KISS lacks definition depth — "keep it simple" is a directive, not a methodology. Same problem as YAGNI (also Tier 1). But it's so widely referenced that excluding it feels wrong.

Detailed Analysis

#354 P.A.R.A. Method — ⚠️ Discuss

• Precise: Yes — four clear categories (Projects, Areas, Resources, Archive)
• Rich: Moderate — primarily an organizational framework, less rich than Diataxis
• Consistent: Yes — well-defined by Forte
• Attributable: Yes — Tiago Forte, "Building a Second Brain"
• Concern: Extends catalog beyond SE into personal productivity. Is that in scope?

#355 PERT — ✅ Accept

• Precise: Very — concrete formula (O+4M+P)/6, network diagrams, critical path
• Rich: Yes — connects estimation, scheduling, probability, risk
• Consistent: Yes — 65+ years of established usage
• Attributable: Yes — Malcolm, Roseboom, Clark, Fazar (1958)
• Tier 2 correct: Useful but specialized (project planning, not daily coding)

#356 Spec-Driven Development — ⚠️ Discuss

• Precise: Moderate — the term is used differently by different people (API-first vs. formal specs vs. our workflow doc)
• Rich: Yes — connects to BDD, TDD, contract-first, verification
• Consistent: Weak — no single canonical definition
• Attributable: Weak — Swagger/Thoughtworks are not the originators; the term is emergent
• Concern: We have a whole workflow document about this. Making it an anchor could create circular references. Also, our evaluation showed EARS (similar domain) scores poorly.

#357 Explicit Contract Surface — ❌ Reject

• Precise: Moderate — describes a pattern but the name is not established
• Rich: Yes — connects ACL, DTOs, mapping, DIP
• Consistent: No — this is not a recognized term in the literature
• Attributable: No — Evans/Martin/Fowler did not coin this term
• This is a design practice, not a semantic anchor. It combines existing anchors (Clean Architecture, DDD, SOLID DIP) but doesn't add a new activation.

#358 Vertical Slice Architecture — ✅ Accept

• Precise: Yes — clear distinction from layered architecture
• Rich: Yes — connects to CQRS, feature cohesion, screaming architecture
• Consistent: Yes — Jimmy Bogard's talks and blog posts are canonical
• Attributable: Yes — Jimmy Bogard
• Tier 3 justified: A well-known alternative to Clean/Hexagonal that LLMs should know

#359 GRASP — ✅ Accept

• Precise: Very — 9 named patterns with clear definitions
• Rich: Yes — foundational OO design patterns, connects to SOLID, GoF
• Consistent: Yes — Craig Larman's "Applying UML and Patterns" is canonical
• Attributable: Yes — Craig Larman
• Tier 3 justified: Standard curriculum material, widely taught

#360 KISS — ⚠️ Discuss

• Precise: Low — "keep it simple" is a directive, not a methodology
• Rich: Low — doesn't activate multiple interconnected concepts
• Consistent: Mixed — everyone agrees on the principle but not on what "simple" means
• Attributable: Yes — Kelly Johnson (Lockheed Skunk Works)
• Tier 1 correctly assigned: Same tier as YAGNI and TIMTOWTDI. Copilot got this right!
• Question: We reference KISS in the workflow doc (AGENTS.md conventions). Rejecting it would be inconsistent.

[raifdmueller]

Thanks for adding KISS! This is a widely referenced principle that we already use in our workflow documentation (AGENTS.md conventions list "DRY, SOLID, KISS, Ubiquitous Language").

Recommendation: merge as Tier 1.

Tier 1 is the right call — KISS is a well-known principle but lacks the definition depth of a full methodology. Same tier as YAGNI and TIMTOWTDI, which is consistent.

We ran it through our evaluation framework and it scores 100% on Claude, GPT-4o, and Mistral Large for L1 Recognition. All major models know it.

One small note: Copilot also added :related: kiss-principle to YAGNI — that's a nice touch, strengthens both anchors.