Guille Fernandez
Community@etrigan16
Gentle Programming skill registry for spec-driven development, pull request hygiene, Go testing, and LLM-first skill authoring.
Agent Skills by Guille Fernandez
Showing 22 vetted skills indexed across 1 GitHub repositories.
sdd-spec
Writes SDD delta specifications with RFC 2119 requirements and Given/When/Then scenarios.
sdd-onboard
Guides users through a complete spec-driven development cycle on a real codebase.
cognitive-doc-design
Structures Markdown documentation to reduce cognitive load for readers and reviewers.
skill-improver
Audit and refactor SKILL.md files against an LLM-first style guide.
sdd-propose
Creates structured SDD change proposals with intent, scope, capabilities, and rollback plans.
sdd-archive
Archives completed SDD changes by merging delta specs into main specs.
sdd-init
Initializes SDD project context, testing capabilities, and skill registry with configurable persistence modes.
chained-pr
Splits oversized pull requests into chained review slices under 400 changed lines.
comment-writer
Write warm, direct collaboration comments for PRs, issues, and reviews.
work-unit-commits
Plans git commits as reviewable work units with tests, docs, and rollback boundaries.
go-testing
Applies focused Go testing patterns including table-driven tests, Bubbletea teatest flows, and golden files.
sdd-design
Generates technical design documents with architecture decisions, file changes, and threat matrices for SDD changes.
skill-creator
Creates LLM-first skill units with valid frontmatter and structured instruction contracts.
sdd-apply
Implements spec-driven development tasks by writing code from specs and design artifacts.
sdd-verify
Verify SDD change implementations by executing tests and validating spec compliance.
skill-registry
Indexes available skills by trigger and path into a registry file.
sdd-tasks
Generates phased implementation task breakdowns from SDD proposals, specs, and designs.
branch-pr
Creates GitHub pull requests with issue linkage, branch naming, and label validation.
_shared
Stores shared SDD reference documents for persistence conventions and phase protocols.
sdd-explore
Investigates codebases and produces structured exploration analyses for spec-driven development changes.
judgment-day
Runs blind dual-judge adversarial code review with bounded fix and re-judgment rounds.
issue-creation
Creates GitHub issues using bug report and feature request templates with label workflows.
Frequently Asked Questions About Guille Fernandez
FAQPage SchemaWhat tasks can I automate using etrigan16's skills?▼
You can run the complete spec-driven development cycle: explore ideas, propose changes, write delta specs, design architecture, break work into tasks, apply implementations, verify against specs, and archive completed changes. Additional skills cover chained PR splitting, issue creation, Go testing patterns, and dual adversarial review.
Who are these skills designed for?▼
Software engineers and teams practicing spec-driven development on real codebases, particularly those managing large pull requests, writing Go tests with Bubbletea teatest or golden files, and authors building or auditing LLM-first skills with structured frontmatter.
How do the SDD skills run in practice?▼
SDD skills are orchestrator-launched and delegate-only, not user-invocable. The orchestrator triggers each phase in sequence: init sets up context and registry, then explore, propose, spec, design, tasks, apply, verify, and archive execute the change lifecycle with synced delta specs.
What licenses cover these skills and are they free?▼
All skills are open source under MIT or Apache-2.0 licenses. The SDD lifecycle skills and skill-registry use MIT, while review, documentation, testing, and skill-authoring skills use Apache-2.0. There is no cost to use or modify them.
What prerequisites do these skills require?▼
SDD skills require an orchestrator to launch them since they are delegate-only and not user-invocable; sdd-init must run first to establish context, testing capabilities, registry, and persistence. Go-testing assumes a Go environment, and PR skills assume GitHub issue-first conventions.