Drive structured software design and delivery: stress-test plans against domain models, generate PRDs, decompose specs into actionable issues, guide TDD with red-green-refactor loops, deepen module design for testability, and journal work from git history — all while maintaining living documentation (CONTEXT.md, ADRs) and handing off context across sessions.
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
Break a plan, spec, or PRD into independently-grabbable slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
Turn the current conversation context into a PRD and save it. Use when user wants to create a PRD from the current context.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Claude Code skills for an AI-assisted development pipeline — from idea to shipped code.
Install all skills globally:
npx skills@latest add adrianfernandezalv/skills -y -g
Install a single skill:
npx skills@latest add adrianfernandezalv/skills skill=<name> -y -g
The installer detects which agents you have installed (Claude Code, Cursor, Codex, etc.) and creates symlinks automatically for each. The skills are written and optimized for Claude Code — behavior on other agents may vary.
The skills are designed to work together end-to-end:
/grill-me → clarify your idea
/grill-with-docs → stress-test against your codebase's domain model
/to-prd → turn the conversation into a structured PRD
/to-issues → break the PRD into independently-grabbable slices
/tdd → implement each slice with red-green-refactor
/improve-codebase-architecture → find deepening opportunities after implementation
/journal → reconstruct today's work from git history (work vs personal)
/handoff → write a handoff comment on the active issue
| Skill | Description |
|---|---|
grill-with-docs | Stress-test a plan against the codebase's domain model (CONTEXT.md, ADRs) and update docs inline |
to-prd | Turn the current conversation into a structured PRD |
to-issues | Break a PRD into independently-grabbable implementation slices |
tdd | Red-green-refactor TDD loop for features and bug fixes |
improve-codebase-architecture | Find refactoring opportunities and deepen module boundaries |
| Skill | Description |
|---|---|
grill-me | Interview to reach shared understanding before starting work |
journal | Reconstruct today's work from git history across your repos, split work vs personal |
handoff | Write a handoff comment on the active issue for the next session |
Four skills (to-prd, to-issues, journal, handoff) persist state across sessions and adapt to a configurable backend. Backends dispatch independently, so combinations (e.g. GitHub issues + Inkdrop journal) work out of the box.
output: in CLAUDE.local.mdSelects where to-prd / to-issues / handoff write. Default is github when the key is absent.
output: | PRD | Slices | Handoff |
|---|---|---|---|
github (default) | Epic tracking issue (label epic), PRD in the body | Native sub-issues of the Epic, type:/status: labels, release as milestone | Comment on the active issue |
jira | Jira ticket description | Child Jira issues with blocking links | Comment on the ticket |
inkdrop | Spec notebook note | Issues notebook notes, type + release tags | ## Handoff section in the issue note |
With github, issue status is tracked by labels (no GitHub Project needed): status: to-define → status: selected-for-dev → status: in-progress → closed (Done); wontfix = dropped. Labels and milestones are created on-demand.
journal-backend in ~/.claude/CLAUDE.md/journal reconstructs the day from git history and writes it where journal-backend says (journal-path gives the location):
journal-backend | Behavior |
|---|---|
obsidian (default) | Writes <journal-path>/<date>.md and commits it (vault is a git repo) |
inkdrop | One note per day in the Journal notebook |
/journal scans journal-roots for repos, attributes commits via journal-emails (all your identities, across all branches), and optionally splits Work vs Personal by journal-work-hosts:
# ~/.claude/CLAUDE.md
journal-backend: obsidian
journal-path: ~/notes/Journal
journal-roots: ~/code # dirs to scan for git repos
journal-emails: [email protected], [email protected]
journal-work-hosts: git.company.com # optional — marks matching repos as "work"
Some skills expect specific files to exist in your project. Create them once and the skills will use them automatically:
| File | Used by | Purpose |
|---|---|---|
CONTEXT.md | grill-with-docs, improve-codebase-architecture, tdd | Domain glossary — canonical terms and relationships for this codebase |
docs/adr/ | grill-with-docs, improve-codebase-architecture | Architectural Decision Records — decisions the skills won't re-litigate |
CLAUDE.local.md | to-prd, to-issues, handoff | Project-level config (output: selects the issue backend; default github) |
CONTEXT.md and docs/adr/ are created lazily by the skills themselves the first time they're needed — you don't have to set them up manually.
Based on mattpocock/skills by Matt Pocock, MIT license.
npx claudepluginhub adrianfernandezalv/skillsNo description provided.
GitHub Project Management workflow for product development: PRD creation, epic/task breakdown, TDD execution, and QA planning
A Claude Code plugin for structured, context-efficient software development.
Virtual development team: TDD, debugging, code review, backlog management, and proven workflow patterns
AI-Driven Engineering workflow commands for managing issues, tasks, implementation, and PRs.
Ultra-compressed communication mode. Cuts ~75% of tokens while keeping full technical accuracy by speaking like a caveman.