Merge pull request #382 from raifdmueller/feat/eval-new-anchors

feat: evaluation specs for GTD, KISS, P.A.R.A.

Author: rdmueller

evaluations/specs/gtd.yaml

@@ -0,0 +1,42 @@
+anchor: gtd
+tier: 3
+questions:
+  recognition:
+    question: 'Which of the following best describes "GTD — Getting Things Done"?
+
+      '
+    options:
+      A: Organize information into four categories — Projects, Areas, Resources, and
+        Archive — to create a comprehensive knowledge management system that connects
+        actionable items with relevant reference materials and long-term goals
+      B: 'Collect everything that has your attention — tasks, ideas, commitments —
+        into trusted external "inboxes" so nothing is held in your head; process each
+        captured item: is it actionable? if yes, define the next physical action.
+        if no, trash it, incubate it, or file it as reference'
+      C: Break down complex tasks into smaller, time-boxed iterations with daily standups
+        and retrospectives to ensure continuous delivery of value while maintaining
+        team velocity and stakeholder alignment throughout the development process
+      D: Establish clear, measurable criteria that must be met before any work item
+        can be considered complete, including code review, testing, documentation,
+        and deployment requirements to ensure consistent quality standards
+    correct: B
+  application:
+    scenario: Sarah is a senior developer juggling multiple code reviews, bug fixes,
+      feature development, and team meetings. She feels overwhelmed because tasks
+      keep slipping through the cracks, and she's constantly worried about forgetting
+      important commitments. She needs a systematic approach to manage her workload
+      without mental stress.
+    anchor_prompt: using GTD — Getting Things Done
+    paraphrase_prompt: What systematic approach should Sarah implement to capture,
+      organize, and manage her various work commitments while reducing mental overhead?
+    options:
+      A: Create a single prioritized to-do list and work through items from top to
+        bottom, updating priorities daily based on urgency and importance.
+      B: Capture all tasks and commitments into trusted external inboxes, then clarify
+        each item by defining specific next actions and organizing them by context
+        (@computer, @meeting, etc.) for efficient execution.
+      C: Use time-blocking to schedule all work in advance, dedicating specific calendar
+        slots for different types of tasks like coding, reviews, and meetings.
+      D: Implement a Kanban board with columns for backlog, in-progress, and done,
+        limiting work-in-progress to maintain focus on current tasks.
+    correct: B

evaluations/specs/kiss-principle.yaml

@@ -1,6 +1,5 @@
 anchor: kiss-principle
 tier: 1
-
 questions:
   recognition:
     question: 'Which of the following best describes the "KISS Principle"?
@@ -16,3 +15,23 @@ questions:
       D: A project management approach that prioritizes delivering minimal viable
         features with the shortest possible development cycles
     correct: A
+  application:
+    scenario: Your team is building a user authentication system for a web application.
+      You're deciding between implementing a simple username/password login with basic
+      session management versus creating a sophisticated multi-factor authentication
+      system with OAuth integration, biometric support, and advanced session analytics.
+      The current requirements only specify that users need to log in securely to
+      access their personal dashboards.
+    anchor_prompt: using KISS Principle
+    paraphrase_prompt: Which approach best balances meeting current requirements while
+      maintaining system maintainability and development efficiency?
+    options:
+      A: Implement the sophisticated multi-factor system immediately to future-proof
+        the application and demonstrate technical expertise to stakeholders.
+      B: Start with username/password authentication and basic session management,
+        then add complexity only when specific security requirements emerge.
+      C: Research and implement the most popular authentication framework used by
+        industry leaders, regardless of current complexity needs.
+      D: Build a custom hybrid solution that combines elements of both approaches
+        to provide maximum flexibility for unknown future requirements.
+    correct: B

evaluations/specs/para-method.yaml

@@ -1,18 +1,44 @@
 anchor: para-method
 tier: 3
-
 questions:
   recognition:
-    question: 'Which of the following best describes the "P.A.R.A. Method"?
+    question: 'Which of the following best describes "P.A.R.A. Method"?
 
       '
     options:
-      A: A software architecture pattern that separates concerns into Presentation,
-        Application, Repository, and Adapter layers
-      B: A knowledge organization framework that categorizes information into Projects,
-        Areas, Resources, and Archive based on actionability
-      C: A prioritization technique that evaluates items by their Probability,
-        Applicability, Risk, and Achievability scores
-      D: A documentation standard that structures technical content into Purpose,
-        Audience, Requirements, and Appendix sections
+      A: 'A documentation framework that categorizes content into four types: tutorials
+        for learning, how-to guides for problem-solving, technical reference for information,
+        and explanations for understanding'
+      B: Short-term efforts with a specific goal and deadline (e.g., "Launch website",
+        "Write article"); long-term responsibilities with a standard to maintain over
+        time (e.g., "health", "finances", "team management")
+      C: A software architecture pattern that separates applications into Presentation
+        layer for user interface, Application layer for business logic, Repository
+        layer for data access, and API layer for external communication
+      D: A task management syntax that uses plain text formatting with priority markers
+        (A), (B), (C), creation dates, completion dates, project tags, and context
+        labels for organizing todo items
+    correct: B
+  application:
+    scenario: You're a senior developer who has accumulated hundreds of notes, code
+      snippets, documentation links, and project files across multiple tools over
+      the past year. Your team is starting three new microservices projects this quarter,
+      you're responsible for maintaining the CI/CD pipeline, and you're also researching
+      GraphQL and Kubernetes for potential future adoption.
+    anchor_prompt: using P.A.R.A. Method
+    paraphrase_prompt: to organize all your information based on how immediately actionable
+      each item is for your current work
+    options:
+      A: Create folders by technology (JavaScript, Python, Docker) and file type (notes,
+        code, docs), then organize current work and research materials within each
+        technology folder based on relevance.
+      B: 'Create four main folders: active microservices work with deadlines, ongoing
+        CI/CD maintenance responsibilities, GraphQL/Kubernetes research materials,
+        and completed or abandoned items from previous quarters.'
+      C: Organize by urgency levels (urgent, important, someday, never) and move items
+        between folders as priorities shift, keeping all active work in the urgent
+        folder regardless of type.
+      D: Group by source and recency (meeting notes, web articles, code repos) with
+        subfolders for this month, last month, and older items, ensuring easy chronological
+        access to information.
     correct: B