Transforms feature requests into structured implementation plans with task breakdowns and TDD requirements.
npx skills add https://github.com/petemcw/farseer --skill planner-petemcw
Please help me install this Agent Skill. Skill: planner Source: https://github.com/petemcw/farseer/tree/main/skills/planner Command: npx skills add https://github.com/petemcw/farseer --skill planner-petemcw
_plan.md with user stories, scope, success criteria, and numbered task files written as exact test descriptions with explicit dependencies forming a valid DAG. - Hook-Based Review Pipeline: Runs pre-plan and post-plan hook agents (e.g., devil's advocate) with fingerprint drift detection to validate the plan before execution. - Use Case: Describe "help me build user authentication with JWT" and receive a feature branch, a plan directory with dependency-ordered task files, and a ready-to-execute plan for the orchestrate skill. ## Quick Start Ask the assistant to help you build a new feature, such as "help me build user authentication with JWT", and it will discover your codebase, ask clarifying questions, and produce a structured task plan.High-intent search queries and answers about installing and using this skill.
Describe the feature in natural language, such as "help me build user authentication". The planner explores your codebase, asks grounded clarifying questions, then writes a plan directory with numbered task files, dependencies, and test-description requirements.
Tasks are thin vertical slices cutting through all integration layers, each with 3-7 requirements written as exact test names. Dependencies are explicitly declared and validated as a DAG so independent tasks can run in parallel batches.
Skip it for quick bug fixes, single-line changes, documentation, or simple questions. Also do not use it to execute an existing plan; running a plan is handled by the orchestrate skill instead.
Yes. If you reference a GitHub issue such as "#18" or an issue URL, the planner records it in the plan's Related Issues field using "Closes #N" or "Relates to #N" depending on whether the plan fully resolves it.
The planner mechanically validates that dependencies form a valid DAG with no circular references. If a cycle is detected, it identifies the conflict and asks you to resolve it before finalizing the plan.
roger8bOrchestrate full-stack application creation from natural language requests.
dopsonbrAutomate approved plan implementation with subagents and verification checkpoints.
uzumaki-incReview architecture, data flow, and testing strategy to lock in an engineering execution plan.
duronextCreate and route tickets across Linear, GitHub Issues, or Jira using jig.config.md.