Skip to content

Instantly share code, notes, and snippets.

View jwiegley's full-sized avatar

John Wiegley jwiegley

View GitHub Profile
{
services.technitium-dns-server = {
enable = true;
openFirewall = true;
};
systemd.services.technitium-dns-server.serviceConfig = {
WorkingDirectory = lib.mkForce null;
BindPaths = lib.mkForce null;
};

name: task-orchestrator description: Use this agent when you need to coordinate and manage the execution of Task Master tasks, especially when dealing with complex task dependencies and parallel execution opportunities. This agent should be invoked at the beginning of a work session to analyze the task queue, identify parallelizable work, and orchestrate the deployment of task-executor agents. It should also be used when tasks complete to reassess the dependency graph and deploy new executors as needed.\n\n\nContext: User wants to start working on their project tasks using Task Master\nuser: "Let's work on the next available tasks in the project"\nassistant: "I'll use the task-orchestrator agent to analyze the task queue and coordinate execution"\n\nThe user wants to work on tasks, so the task-orchestrator should be deployed to analyze dependencies and coordinate execution.\n\n\n\n\nContext: Multiple independent tasks are available in the queue\nuser: "

task-master init
task-master models --setup
claude --model opus --dangerously-skip-permissions "Please read the project description in @prd.txt and produce a full and complete Product Requirements Document (PRD) in a Markdown file prd.md that I can use to build the full application."
task-master parse-prd prd.md
task-master list
task-master analyze-complexity --research
task-master expand --all
task-master rules add claude
task-master validate-dependencies
claude --model opus --dangerously-skip-permissions /run-orchestrator
# Project Requirements Document
## GNU Emacs Codebase Performance Analysis
### 1. Executive Summary
This project aims to conduct a comprehensive performance analysis of the GNU Emacs codebase, identifying and documenting all potential performance issues that could impact system resources, user experience, and application stability. The analysis will cover both platform-agnostic C code and platform-specific implementations, with particular emphasis on the macOS/NeXTstep (NS) port.
An example of some of the issues that might be considered can be found in the file PERFORMANCE_ANALYSIS.md.
### 2. Project Objectives
Debugger entered--Lisp error: "Making gptel-model buffer-local while locally let-bound!"
make-local-variable(gptel-model)
gptel--sanitize-model()
gptel-request(("*** TASK Provide roadmap options to John tomorrow including lean path and alternatives :Jesse:\n:PROPERTIES:\n:OFFSET: 32:35\n:LAST_REVIEW: [2025-08-09 Sat]\n:NEXT_REVIEW: [2025-08-09 Sat]\n:REVIEWS: 1\n:ID: 7BA3D39A-3D68-4042-B206-BE96C24163CA\n:CREATED: [2025-08-09 Sat 10:54]\n:LOCATION: 38.569498,-121.388618\n:END:\n*** TASK Schedule follow-up meeting next week to continue prioritization discussions :Jesse:\n:PROPERTIES:\n:OFFSET: 33:01\n:LAST_REVIEW: [2025-08-09 Sat]\n:NEXT_REVIEW: [2025-08-09 Sat]\n:REVIEWS: 1\n:ID: 4AF0BAC1-0253-4BC8-9534-075183776F47\n:CREATED: [2025-08-09 Sat 10:54]\n:LOCATION: 38.569498,-121.388618\n:END:\n" "What is the required change?" "Shorten it as described.") :dry-run nil :system "Given a list of tasks, shorten the title so that it is no longer than 67 characters long. You can move th
{
"model": "athena/Qwen3-30B-A3B-Thinking-2507",
"messages": [
{
"role": "system",
"content": "You are a helpful assistant. Respond concisely."
},
{
"role": "user",
"content": [
*Prompt*: What is the best Emacs command for filtering items in the Org-mode agenda view?
*Response*:
#+begin_tool (find_functions :keyword ["org-agenda-filter" "org-agen ...)
(:name "find_functions" :args (:keyword ["org-agenda-filter" "org-agenda-filter-by" "org-agenda" "filter" "agenda" "org"]))
Functions containing '[org-agenda-filter org-agenda-filter-by org-agenda filter agenda org]':
org-agenda-filter-by-category Filter lines in the agenda buffer that have a specific category.
org-agenda-filter-by-effort Filter agenda entries by effort.
(pretty-hydra-define
multiple-cursors
(:color teal :quit-key "q")
("Mark/Unmark"
(("c" mc/mark-all-dwim "DWIM")
("A" mc/mark-all-in-region "in region")
("r" mc/mark-all-regexp "regexp")
("%" mc/mark-all-in-region-regexp "re in region")
("<C-m> ." ace-mc-add-multiple-cursors "ace add")
("<C-m> M-." ace-mc-add-single-cursor "ace add sing")
;;; -*- lexical-binding: t -*-
(require 'cl-lib)
(let* ((mutex (make-mutex))
(cond-var (make-condition-variable mutex))
waiting
(thread-a
(make-thread
#'(lambda ()

PARA and the value of meaningful distinctions

There have been many trends in the data and task management world, from day planners, to GTD, to bullet journals, to the PARA method – and many more. This article takes a look at PARA in particular, but also pulls back a bit as