skills.rest
finas
finasCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

AI Agent Skill: Spec-Driven Development for yaccm

Implement yaccm features by reading spec documents and mapping changes to requirement IDs.

Updated Apr 13, 2026
Search Tags:#testing#spec-driven#implementation#swift#requirement traceability#component boundaries#macos clipboard
One-click install
npx skills add https://github.com/finas/tiny_maccy --skill ai-agent-skill-spec-driven-development-for-yaccm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: AI Agent Skill: Spec-Driven Development for yaccm
Source: https://github.com/finas/tiny_maccy/tree/main
Command: npx skills add https://github.com/finas/tiny_maccy --skill ai-agent-skill-spec-driven-development-for-yaccm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps AI agents implement the yaccm clipboard manager without guesswork by enforcing a strict spec-first workflow tied to the project’s architecture boundaries and test plan.

Core Features & Use Cases

  • Spec-driven implementation loop: Read functional, architecture, UX (when relevant), then test-plan documents before writing code.
  • Requirement-to-code traceability: Ensures every change maps back to requirement IDs (e.g., REQ-KBD-002) to prevent scope drift.
  • Correct component boundaries: Enforces separation of concerns across ClipboardManager, PopupWindowController, ClipboardPopupView, StatusBarController, and HotKeyManager.
  • Build and smoke-test verification: Guides how to compile and validate MVP acceptance behavior via manual smoke tests and spec compliance.
  • Safe iteration and error handling: Provides a disciplined strategy for fixing build failures and behavior mismatches by re-checking the relevant requirement.

Quick Start

Ask the AI agent to implement REQ-KBD-002: when the user presses Return, flash the selected row for 300 ms and then close the popup, while keeping changes confined to the correct controller/view components and verifying with the specified build and smoke tests.

Frequently Asked Questions about AI Agent Skill: Spec-Driven Development for yaccm

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement Swift clipboard manager features without violating the spec?▼

Spec-driven development for Swift clipboard managers requires reading functional, architecture, UX, and test-plan documents sequentially before writing code. This ensures every change maps to requirement IDs, preventing scope drift and unverified behavior across hotkey, popup, and persistence components.

What is requirement traceability in spec-driven development?▼

Requirement traceability in spec-driven development means mapping every code change directly back to specific requirement identifiers like REQ-KBD-002. This mechanism prevents scope drift by ensuring implementation decisions are driven by documented functional and architecture specifications.

How do I enforce component boundaries when building a macOS clipboard manager?▼

Enforcing component boundaries for a macOS clipboard manager involves restricting code edits to designated sources and maintaining strict separation of concerns across ClipboardManager, PopupWindowController, ClipboardPopupView, StatusBarController, and HotKeyManager components.

How do I validate Swift build behavior and spec compliance for macOS apps?▼

Validating Swift build behavior and spec compliance involves compiling the project via swift build and executing a defined manual smoke-test checklist. This verifies MVP acceptance behavior and ensures implementations match the specified functional requirements.

Why does my spec-driven implementation fail due to missing spec context?▼

Spec-driven implementation fails when missing spec context causes unclear component ownership and unverified behavior. Resolving this requires a disciplined strategy of re-checking the relevant requirement identifier and sequentially reading all functional, architecture, and test documents.

Does spec-driven development work for iterative Swift UI changes like popup interactions?▼

Spec-driven development works for iterative Swift UI changes by applying requirement-driven implementation loops to popup behavior, search, and keyboard interactions. Changes are validated through swift build and manual smoke tests to ensure acceptance behavior is maintained.

Related Skills

Explore More Software Engineering Skills→
mbwsimsmbwsims
71

test-plan

Generate structured test plans for code without writing test code.

Community
Intermediate
NNPopovNNPopov
2

feature-validation

Generate validation.md with UX test scenarios and code review checklists for Flutter feature slices.

Community
Intermediate
leaderiopleaderiop
7

Advanced Testability Ai Ergonomic

Enforce explicit contracts and observable patterns for testable, LLM-friendly code.

Community
Advanced
zabinyzabiny
2

backend-patterns

Standardize backend architecture patterns for Klabis Spring Modulith modules.

Official
Advanced