Plan large work efforts as decision-ticket maps on an issue tracker.
npx skills add https://github.com/petemcw/farseer --skill farseer-petemcw
Please help me install this Agent Skill. Skill: farseer Source: https://github.com/petemcw/farseer/tree/main/skills/farseer Command: npx skills add https://github.com/petemcw/farseer --skill farseer-petemcw
farseer:map) with a named destination, notes, decisions-so-far index, and a Not Yet Specified section for unresolved fog. - Decision Tickets: Creates child issues typed as research, prototype, interviewing, or task, wired with native blocking relationships so the frontier of takeable work is visible in the tracker UI. - Session-Based Resolution: Works one ticket per session, recording answers as resolution comments and graduating newly specifiable fog into fresh tickets. - Use Case: You have a vague goal like migrating a data structure or producing a spec. Invoke the skill to interview you, chart the decisions ahead as tickets, fire off research subagents in parallel, and then work through the frontier ticket by ticket across sessions. ## Quick Start Ask the agent to chart a map for your large idea, for example: "Use farseer to plan the migration of our legacy data model to the new schema."High-intent search queries and answers about installing and using this skill.
Invoke the skill with your loose idea. It interviews you to name the destination, maps the frontier breadth-first, creates a map issue labeled farseer:map, and files the specifiable decisions as child tickets wired with blocking relationships.
A decision ticket is a question whose resolution is a decision, never a slice of build work. Each ticket is a child issue of the map, typed as research, prototype, interviewing, or task, and sized to fit one agent session.
The map and tickets live on whatever issue tracker the repo is configured with via /farseer:repo-setup. Trackers with native blocking render the frontier directly; those without fall back to a body convention, and local-markdown is the default.
Yes. A session claims a ticket by assigning it before starting work, so concurrent sessions skip claimed tickets. The frontier is the set of open, unblocked, unclaimed child issues, and each session resolves at most one ticket.
Skip the map when charting surfaces no fog, meaning the path to the destination is already clear and the work fits in one session. Also avoid it for pure execution work, since tickets resolve decisions rather than deliver build slices.
jchildreeConfigure repository engineering skills, issue tracker, triage labels, and documentation settings.
bjornslibCoordinate autonomous multi-agent software initiatives with Agent Teams and Beads tracking.
HexSleevesChallenges a plan or design to expose weaknesses before execution.
pytholicDecompose confirmed software goals into ordered implementation plans with verifiable tasks.