JarrydAdaens
- 27 skills
- 0 followers
- 6 hours ago last updated
- ▌ Evidence · jarrydadaens bundleUse this skill when the user explicitly asks for evidence capture, provenance, validation evidence, source-grounded proof, or an evidence.md file during an agentic task. It maintains an opt-in evidence record — by default the `## Evidence / References` section inside the active plan.md, or a standalone evidence.md when explicitly requested or genuinely required for audit — that indexes changed files, commits, checks, planning inputs, and unverified claims.
- ▌ Handover · jarrydadaens bundleUse this skill when the user explicitly asks for a handover, ownership transfer, continuation note, shallow handover, or summary artifact after agentic work. It reviews conversation context when available, recent git history, plan.md, implementation-log.md, and optional thinking.md, evidence.md, and complaining.md to produce a grounded shallow handover file.
- ▌ Complaining · jarrydadaens bundleUse this skill when an agent should record genuine blockers, friction, ambiguity, tool failures, bad assumptions, risky constraints, or other execution problems while it works. By default, complaints go into the active plan's `## Complaints / Friction` section or are raised directly to the user; a standalone complaining.md is opt-in, for explicit requests or long-running workflows that need durable friction tracking.
- ▌ Rails Planning · jarrydadaens bundleUse this skill when creating, revising, locating, or enforcing implementation plans inside an Agentic Rails project. Use for implementation plans, work plans, execution plans, feature plans, bug plans, repository planning before coding, IDE planning drift, or any planning output that should survive across IDEs, machines, branches, sessions, reviews, retrospectives, execution logs, evidence, complaints, or handovers. The skill ensures plans are written into the target repository under context/implementation-plans/<milestone-slug>/ <story-slug>/, producing one primary artifact — plan.md — with CER, questions, evidence, complaints, execution log, and completion review folded into it by default. Can also produce opt-in sidecars (evidence.md, complaining.md, thinking.md) beside plan.md when a story genuinely needs durable, separately tracked provenance.
- ▌ Mermaid Scout · jarrydadaens bundleUse this skill when discovering files and filtering them to specific classes or types for a Mermaid relationship map. It writes scoutmap.md as a CSV-like work queue for scoped inventory or for the mermaid-mapper workflow.
- ▌ Rails Grade Cer · jarrydadaens bundleUse this skill to grade an Agentic Rails plan on three orthogonal axes — complexity, effort, and risk (CER) — and emit a score card. Use whenever the user wants a plan sized, graded, or assessed before dispatch; wants to know how hard, how long, or how dangerous a plan is; wants to spot a story that should be reclassified as an epic; or wants CER scores to feed a downstream routing or planning system. Runs all three axes by default, or any subset the user names (e.g. "just the risk", "effort and complexity"). Grades only — it does not route, plan, fragment, select models, or suggest fixes.
- ▌ Mermaid Mapper · jarrydadaens bundleUse this skill when converting a bounded source file or type list into Mermaid relationship edges for inheritance, composition, dependencies, and constructor-injected collaborators. Use standalone for one file/class or as a worker chunk in the mermaid-mapper workflow.
- ▌ Check Dot Agent · jarrydadaensUse this skill when the user wants to verify whether an agentic IDE or tool can discover and run skills from the global `%USERPROFILE%\\.agents` folder. When active, output the exact validation text in chat and do not add extra commentary.
- ▌ Rails New Proposal · jarrydadaens bundleUse this skill when the user wants to capture a proven, project-local innovation - a guard rail, hook set, agent, rule pack, script, or workflow - as a self-contained proposal for the Agentic Rails tooling repository. Triggers: "make this a proposal", "propose this for rails", "bundle this up for tooling", "this guard rail should be generalized". It copies the working slice verbatim (hooks extracted into a fresh .claude/settings.json, agents, scripts, dependency manifests, docs) into proposals/<slug>/ in the tooling repo, writes a README recording the use case, the evidence it works, and a suggested destination, and can zip the proposal for sharing with another developer. It is drop-off only: it never integrates anything into source/, never generalizes code, and never touches other proposals.
- ▌ Thinking Out Loud · jarrydadaens bundleUse this skill when the user explicitly asks for thinking out loud, sanitized thinking notes, investigation notes, or a durable thinking.md file during an agentic task. It maintains an opt-in project-local thinking artifact that captures useful investigation paths, discovered constraints, observations, and revisit items without exposing private chain-of-thought.
- ▌ Mermaid Validation · jarrydadaensUse this skill when validating a Mermaid graph fragment before accepting mapper output or merging partials. It checks structure, scope, and reference plausibility, then returns pass or fail with concrete reasons.
- ▌ Mermaid Aggregation · jarrydadaensUse this skill when merging accepted Mermaid edge fragments into one diagram. It deduplicates lines, optionally sorts them, wraps them in graph TD and a mermaid code fence, then writes mermaid.md for the workflow or returns the block when used standalone.
- ▌ Rails Retrospective · jarrydadaens bundleUse this skill after implementation work, planning work, Agentic Rails implementation-plan execution, bulk planning, orchestration runs, or completed stories when the user asks for a retrospective, lessons learned, post-work review, process review, plan-adherence review, or durable retrospective.md grounded in plans, logs, git history, changed files, and optional provenance artifacts.
- ▌ Rails Planning Phaser · jarrydadaens bundleUse this skill to fracture a plan into sequential, executable phases. It grades the plan with CER, and if any axis breaches threshold it splits the plan at natural seams into small phases that each fit under the local model's threshold, re-grades every phase, and rewrites the original plan into a manifest that registers and tracks them. Use whenever a plan is too large, complex, or risky to run as one unit; when work needs to be sized for a local model; or when preparing a plan for orchestrated sub-agent execution. Assigns each phase a model tier and escalates to the human if the work needs more than seven phases (it's really multiple stories) or can't be reduced below threshold.
- ▌ Rails Memory Learnings · jarrydadaens bundleUse this skill at the end of a work session - after implementation, planning, Agentic Rails implementation-plan execution, bulk planning, orchestration, or a completed story - when the user asks to capture learnings, memorize the session, write a session learning, or deposit a memory artifact. It reflects on the session and writes exactly one durable learning file into the Rails memory repository's learnings/new/ folder, recording the outcome, what went well, what struggled, and full provenance: the models, harness, thinking effort, reasoning vs non-reasoning, fast mode, and token cost behind the work.
- ▌ Rails Pair Programming · jarrydadaens bundleUse this skill when the user explicitly wants a structured Agentic Rails pair-programming session, such as "use rails-pair-programming", "start rails-pair-programming", "pair program this under Rails", or similar phrasing. The skill establishes intent, gathers the current Story and implementation-plan context from the context tier system, runs a collaborative tutoring and pair-programming loop, and creates a uniquely named session artifact at wrap-up.
- ▌ Rails Clean Frontmatter · jarrydadaens bundleUse this skill to normalize and repair YAML front matter across an Agentic Rails repository: remove junk fields, enforce one metadata.version shape, guarantee name and description, and apply the correct agentic_rails_source_version policy. It auto-selects one of three modes — tooling repo, context starter, or a project derived from the starter — and aborts in repositories that do not use Agentic Rails.
- ▌ Rails Project Appraisal · jarrydadaens bundleUse this skill when the user asks for a deep project appraisal, project audit, architecture review, viability review, strategic review, or "is this project worth continuing?" analysis of an Agentic Rails project. It reads repository and context-tier material, validates the codebase by building, testing, and (where a UI exists) launching it, inspects git history, performs external grounding via web research, and writes a frank, evidence-led markdown report under context/reports/ that grades the project and recommends a course of action — continue, refine, harden, pivot, split, rebuild, freeze, or abandon. Reserved for deep, deliberate use on projects that matter, not a lightweight orientation pass, a code-execution skill, or a normal planning/implementation workflow.
- ▌ Rails Milestone Planning · jarrydadaens bundleUse this skill to turn the story backlog (an unscheduled story inventory, informally "Milestone -1") and the Design doc's Milestones Index into a scored, dependency-ordered story list inside a Milestone document, and to keep the backlog itself alive over time. Use it to pull backlog stories into a fresh milestone's story list, or to refine an existing milestone whose story list has grown past a sensible scope and needs stories shunted into Deferred / Follow-up Work. Calls the rails-grade-cer skill for scoring rather than reimplementing it, and promotes epic-sized backlog items into their own Milestone documents when CER exposes them. Not model-invocable — the user calls this by name when they are ready to plan or refine a milestone's story list; it does not trigger itself on ambient planning conversation.
- ▌ Rails Plan Spam Workflow · jarrydadaens bundleUse this orchestration skill when turning stories, feature descriptions, backlog items, or design notes into many implementation-plan documents. The Boss builds a durable planning queue, dispatches one subagent per story or feature cluster, writes plans, updates progress, and repeats until complete.
- ▌ Commit History Workflow · jarrydadaens bundleUse this skill when summarizing exactly one existing commit from repository history for research-grade commit-history stitching. It inspects commit metadata, diffs, and changed files, then returns one structured JSON record. Do not use it for new commit messages or branch summaries.
- ▌ Mermaid Mapper Workflow · jarrydadaens bundleUse this orchestration skill when building a Mermaid diagram of a large object-oriented codebase from a user-supplied entry point or query. The Boss coordinates scout discovery, parallel mapper chunks, validation, aggregation, and artifacts under documentation/workflows/mermaid_mapper.
- ▌ Skill Template · jarrydadaensUse this template when creating a new Agent Skill that needs valid SKILL.md frontmatter, concise trigger guidance, workflow instructions, examples, and validation notes.
- ▌ Rails Update From Starter · jarrydadaens bundleUse this skill when updating a project derived from Agentic Rails so its project-local context files, templates, front matter, framework metadata, and standard documentation structure stay aligned with a local checked-out agentic_rails_context_starter source of truth. Use when refreshing derived Agentic Rails projects from the current milestone-centric starter without overwriting project-specific design, milestones, backlog stories, historical implementation plans, or provenance. Includes a compatibility layer that migrates projects still on an older, legacy context layout (a single milestones.md, goals files, a tier0/ or Documentation/ root, or a prior generation where milestones only indexed stories kept elsewhere) forward to the current context tier system.
- ▌ Rails Boss Execute Workflow · jarrydadaens bundleUse this orchestration skill when implementing work from design documents, milestone documents, backlog stories, or implementation plans. The Boss reads the supplied documents, builds a durable story/work queue, dispatches one subagent per story or tightly bound plan slice, enforces specialist agents when required, updates progress, and repeats until the requested work is done or blocked.
- ▌ Rails Initialize From Tier0 · jarrydadaens bundleUse this skill when initializing or populating a newly created repository from the Agentic Rails context starter using a large dictation intake document, dictated project seed, AI-generated research report, transcript, rough requirements dump, or kickoff notes. Use it to preserve the raw dictation, synthesize project-specific left-rail context, replace starter placeholders in design (with its Milestones Index), milestone docs, the story backlog, README, and related context files, and optionally seed initial implementation plans without overwriting reusable Agentic Rails framework material.
- ▌ Skill Template Advanced · jarrydadaens bundleUse this template when creating a broad Agent Skill that needs progressive disclosure, focused reference files, routing guidance, examples, and validation without loading all domain knowledge up front.