primax79
Community@primax79 · Pisa (Italy)
primax79 publishes methodology skills for orchestrating delegated coding work: role-to-model mapping, task specification, git-worktree handoffs, conflict resolution, and delegation ROI analysis.
Agent Skills by primax79
Showing 7 vetted skills indexed across 1 GitHub repositories.
primax79interactive-role-setup
Maps abstract role profiles to available AI models and persists the mapping to roles.toml.
primax79headless-executor-contract
Defines behavioral rules for AI agents executing delegated background coding tasks.
primax79delegation-roi-analysis
Analyze delegation cost, defect patterns, and cancellation rates from Executor telemetry.
primax79task-delegation
Applies fixes to an Executor agent's git worktree using git plumbing when file-edit tools are blocked.
primax79task-spec-authoring
Write Executor task specifications and calibrate verification depth for delegated implementation work.
primax79conflict-resolver
Resolve merge conflicts in files produced by parallel Executor tasks.
primax79orchestration-methodology
Orchestrate delegated coding tasks through a six-phase Architect/Executor methodology.
Frequently Asked Questions About primax79
FAQPage SchemaWhat tasks can I accomplish with primax79's skills?▼
You can map role profiles to available models in roles.toml, author Executor task specifications with calibrated verification depth, delegate work via git worktrees, resolve merge conflicts from parallel tasks, and run ROI analysis comparing delegation cost against inline generation.
Who are primax79's orchestration skills designed for?▼
They target engineers and operators running an Architect/Executor pattern, where an orchestrating entity delegates background coding tasks to a zero-interactivity Executor. Both protocol-agnostic methodology skills and manual git-worktree operational skills are included.
How do the task-delegation and task-spec-authoring skills differ?▼
task-spec-authoring covers writing the specification itself: granularity, the negative-claim rule, reference-drift, caller-tracing, and one-task-one-commit. task-delegation covers the manual git-worktree mechanics of handing off that spec and safely interacting with the Executor's live branch afterward.
Do these skills depend on a specific dispatch protocol?▼
No. The headless-executor-contract, task-spec-authoring, and orchestration-methodology skills are explicitly protocol-agnostic, applying whether delegation happens over MCP, a command-line wrapper, or manual handoff. Only task-delegation is specific to the manual git-worktree path.
How does delegation-roi-analysis measure whether delegation pays off?▼
It compares delegation cost against hypothetical inline-generation cost, reviews defect patterns from logged issues, and proposes feedback loops for better task specifications. It is methodology only; concrete telemetry calls live in the specific binding's own repository, such as kilo-mcp's mcp-metrics-analyst.