alycda

---

name: sprinter description: Orchestrates plan → execute → retro pipelines across one or more sprints derived from Linear tickets, using Hermes Kanban as the durable substrate. Decomposes a Linear parent ticket (or single ticket) into sprint-sized chunks, creates a Kanban task pipeline per sprint, and wires retro outputs from sprint N to feed sprint N+1's planner. Use when the user wants to plan, execute, or retro multiple sprints across a Linear ticket with subissues — phrases like "plan sprints from this Linear ticket", "kick off SDKS-XXXX sprint", "orchestrate the SDK work", "set up sprints for the parent ticket". Wraps the existing sprint-planner / sprint-execute / sprint-retrospective skills as the per-sprint specialists; this skill is the cross-sprint orchestrator. version: 0.1.0 metadata: hermes: tags: [sprint, orchestration, kanban, linear, multi-sprint] category: orchestration requires_tools: [kanban_create, kanban_link] requires_toolsets: [linear]

alycda

name	researcher
description	Bootstraps a research-driven project end-to-end using StrongDM's Software Factory pattern. Generates a SEED.md, drafts a research brief, runs parallel deep-research sub-agents (Anthropic-only by default; multi-provider via Hermes profiles when --external is passed), downloads materials, and builds a semantic index. Trigger when the user wants to start a new project that needs systematic prior-art collection — phrases like "prior art", "research brief", "set up factory", "seed and research", "compound engineering", "bootstrap a project", or any reference to the multi-step pipeline. Do NOT use for one-off questions, single web searches, or projects that already have docs/research/index/ built.
version	0.2.0
metadata	hermes tags category research factory prior-art seed deep-research research

alycda

{
	"name": "Rust Development",
	"image": "mcr.microsoft.com/devcontainers/rust:1-bookworm",

	"customizations": {
		"vscode": {
			"extensions": [
				"anthropic.claude-code",
				"rust-lang.rust-analyzer",
				"tamasfe.even-better-toml",

alycda

{
  outputs = { self, ... }: {
    homeManagerModules.zsh = import ./zsh.nix;
  };
}

alycda

_:

[
  # Development Tools
  claude
  visual-studio-code
  warp
  docker-desktop
  
  # Communication Tools

alycda

"""Adding a forecasting and amortization feature to Beancount via a plugin

see https://github.com/beancount/beancount/blob/ab3fdc613fd408e5f6d8039b2fe7eb37c0b31a5e/experiments/plugins/forecast.py
also https://github.com/beancount/beancount/blob/d841487ccdda04c159de86b1186e7c2ea997a3e2/beancount/parser/lexer.l#L127-L129

This entry filter plugin uses existing syntax to define and automatically
insert future transactions based on a convention.

A User can create a transaction like this:

alycda

{ pkgs ? import <nixpkgs> {} }:

pkgs.mkShell {
  buildInputs = [ pkgs.cheat ];

  shellHook = ''
    ln -sf $(pwd)/cheat-config ~/.config/cheat
  '';
}

alycda

let
  nixpkgs = fetchTarball "https://github.com/NixOS/nixpkgs/tarball/nixos-24.05";
  pkgs = import nixpkgs { config = {}; overlays = []; };
in

# https://nixos.org/manual/nixpkgs/unstable/#sec-pkgs-mkShell-variants
pkgs.mkShellNoCC {
  packages = with pkgs; [
    cowsay
    lolcat

alycda

#!/usr/bin/env -S cargo +nightly -Zscript
---cargo
[dependencies]
smol = "2"
---

use std::fmt::Debug;
use std::future::{self, Future};
use std::time::Duration;
use smol::{Timer, io};

alycda

{
	"image": "mcr.microsoft.com/devcontainers/universal:2",
	"features": {
		"ghcr.io/devcontainers/features/rust:1": {
			"version": "latest",
			"profile": "complete"
		}
	},
	"customizations": {
		"vscode": {