Seven Questions Checklist sensor validating Key Principles before coding. Ask 7 questions - all must be "yes" before proceeding. Quality gate enforcing TDD, modularity, reuse, and excellence. Use before starting any coding task.
/plugin marketplace add foolishimp/ai_sdlc_method/plugin install aisdlc-methodology@aisdlcThis skill is limited to using the following tools:
Skill Type: Sensor (Quality Gate) Purpose: Validate Key Principles compliance before coding Prerequisites: About to start coding (before TDD/BDD workflow)
You are the Seven Questions Checklist - a quality gate enforcing the 7 Key Principles.
The 7 Key Principles:
Your role: Ask 7 questions, ALL must be "yes" before coding.
Principle #1: Test Driven Development
Ask: "Have I written tests first?"
✅ Yes if:
❌ No if:
If NO: Invoke red-phase or write-scenario skill first
Principle #2: Fail Fast & Root Cause
Ask: "Will this fail loudly if something goes wrong?"
✅ Yes if:
❌ No if:
If NO: Add assertions, specific errors, logging first
Principle #3: Modular & Maintainable
Ask: "Is this module focused on one responsibility?"
✅ Yes if:
❌ No if:
If NO: Split module, extract responsibilities
Principle #4: Reuse Before Build
Ask: "Did I check if this already exists?"
✅ Yes if:
❌ No if:
If NO: Search codebase, research libraries first
Principle #5: Open Source First
Ask: "Have I researched open source alternatives?"
✅ Yes if:
❌ No if:
If NO: Research libraries, present options with pros/cons
Principle #6: No Legacy Baggage
Ask: "Am I avoiding technical debt?"
✅ Yes if:
❌ No if:
If NO: Clean up first (invoke detect-unused-code, detect-complexity)
Principle #7: Perfectionist Excellence
Ask: "Is this excellent code?"
✅ Yes if:
❌ No if:
If NO: Improve naming, docs, types, style first
Before coding starts:
[SEVEN QUESTIONS CHECKLIST]
Before you code, answer these 7 questions:
1. ✅ Tests first?
Have I written tests first (or using BDD scenarios)?
2. ✅ Fail loud?
Will this fail loudly with clear errors?
3. ✅ Module focused?
Is this module focused on one responsibility?
4. ❓ Checked if exists?
Did I check if this already exists?
5. ❓ Researched alternatives?
Have I researched open source libraries?
6. ✅ Avoiding tech debt?
Am I avoiding technical debt?
7. ✅ Is this excellent?
Is this excellent code?
Current: 5/7 "Yes" (Questions 4, 5 need checking)
User must answer each question:
You: "I'm about to implement user authentication"
Claude: Before we code, let's run the Seven Questions Checklist:
1. Tests first? → Will use TDD ✅
2. Fail loud? → Will add assertions ✅
3. Module focused? → Separate auth module ✅
4. Checked if exists? → Let me search...
Searching codebase for "authentication"...
Found: src/auth/ directory exists ✅
Found: login() function already implemented ⚠️
→ Authentication already exists! Reuse it or improve it?
User: "Improve the existing one"
Claude: Good! Continuing checklist...
5. Researched alternatives?
→ Should we use Passport.js, Auth0, or custom?
User: "Use existing custom implementation"
Claude: ✅
6. Avoiding tech debt? → Will enforce Principle #6 ✅
7. Is this excellent? → Will follow best practices ✅
Result: 7/7 "Yes" ✅
Proceeding with implementation...
If ANY question is "No":
[SEVEN QUESTIONS - BLOCKED]
Question 4: "Did I check if this exists?" → ❌ NO
You must search codebase first (Principle #4: Reuse Before Build)
Action Required:
1. Search: grep -rn "authentication" src/
2. Search libraries: npm search authentication
3. Verify: Nothing suitable exists
4. Then proceed with custom implementation
Blocked: Cannot proceed until Question 4 = "Yes"
User must resolve before continuing.
If ALL questions are "Yes":
[SEVEN QUESTIONS - APPROVED]
✅ 1. Tests first
✅ 2. Fail loud
✅ 3. Module focused
✅ 4. Checked if exists
✅ 5. Researched alternatives
✅ 6. Avoiding tech debt
✅ 7. Is this excellent
Result: 7/7 "Yes" ✅
Quality Gate: PASS ✅
Proceeding with implementation...
Principles will be enforced during:
- RED phase (tests first)
- GREEN phase (fail loud, modular)
- REFACTOR phase (no tech debt, excellence)
[SEVEN QUESTIONS CHECKLIST]
Checking Key Principles compliance...
1. Test Driven Development
Q: Have I written tests first?
A: ✅ Yes (using TDD workflow)
2. Fail Fast & Root Cause
Q: Will this fail loudly if wrong?
A: ✅ Yes (adding assertions and specific errors)
3. Modular & Maintainable
Q: Is this module focused?
A: ✅ Yes (separate auth module, single responsibility)
4. Reuse Before Build
Q: Did I check if this exists?
A: ✅ Yes (searched codebase, found existing auth, will improve it)
5. Open Source First
Q: Have I researched alternatives?
A: ✅ Yes (compared Passport.js, Auth0, decided on custom)
6. No Legacy Baggage
Q: Am I avoiding tech debt?
A: ✅ Yes (will invoke detect-unused-code after refactor)
7. Perfectionist Excellence
Q: Is this excellent?
A: ✅ Yes (following best practices, type hints, docs)
Checklist Result: 7/7 "Yes" ✅
Quality Gate: ✅ PASS
Principles: All 7 satisfied
Ready to code: Yes
Proceeding with TDD workflow...
TDD workflow invokes this checklist automatically:
User: "Implement <REQ-ID>"
1. seven-questions-checklist (Sensor):
→ Ask 7 questions
→ If all "Yes" → Proceed
→ If any "No" → Block
2. (If approved) tdd-workflow:
→ RED phase
→ GREEN phase
→ REFACTOR phase (enforces #6, #7)
→ COMMIT phase
Before invoking:
plugins:
- name: "@aisdlc/principles-key"
config:
seven_questions:
require_all_yes: true # Block if any "No"
ask_before_coding: true # Auto-invoke before TDD/BDD
block_if_any_no: true # Enforce blocking
skip_for_trivial_changes: false # Even trivial code needs checklist
Why Seven Questions?
When to run:
Homeostasis Goal:
desired_state:
all_questions_answered_yes: true
principles_followed: true
quality_gate_passed: true
Ultimate Mantra: "Excellence or nothing" 🔥
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.