Generate follow-on GitHub issues after verifying an end-to-end spine via fak CLI.
npx skills add https://github.com/anthony-chaudhary/fak --skill spine-fanout
Please help me install this Agent Skill. Skill: spine-fanout Source: https://github.com/anthony-chaudhary/fak/tree/main/.claude/skills/spine-fanout Command: npx skills add https://github.com/anthony-chaudhary/fak --skill spine-fanout
This skill solves the problem of fragmented or delayed project delivery by enforcing a disciplined workflow that prioritizes a minimal end-to-end spine before generating a comprehensive follow-on task backlog.
Use the spine-fanout skill to generate the follow-on issue backlog for the current feature after verifying the minimal end-to-end spine is functional.
High-intent search queries and answers about installing and using this skill.
Automate follow-on issue generation by enforcing a spine-first development workflow that verifies a minimal end-to-end implementation before fanning out a structured backlog of 3 to 50+ tasks for QA, dogfooding, and productization via the fak CLI.
Spine-first development is a disciplined workflow methodology requiring a verified, runnable end-to-end path before expanding into secondary tasks. This approach prevents fragmented project delivery by gating automated backlog generation behind a functional core implementation.
Prevent fragmented delivery by enforcing a spine gate that requires a minimal end-to-end feature implementation to be functional before generating any follow-on task backlog. This ensures systematic tracking and deterministic generation of secondary requirements like documentation and testing.
Yes, the fak CLI supports deterministic issue generation, milestone assignment, and deduplication of project work items. It automatically structures 3 to 50+ follow-on tasks while systematically removing duplicate project work.
Generate a follow-on issue backlog when a new feature, library, or process documentation requires systematic tracking of secondary requirements. The workflow applies after verifying the core end-to-end spine is functional, ensuring QA and productization tasks are not forgotten.
Track secondary requirements by automating fan-out to generate a structured list of 3 to 50+ follow-on issues for dogfooding and productization. This ensures nothing is forgotten by enforcing a runnable end-to-end path before backlog creation.
klaaayGenerate detailed implementation plans with file paths, code samples, and verification steps.
catu-aiClassify and label GitHub issues for the easyharness repository.
eric-sabeCreate and manage GitHub issues with templates via gh CLI.
MarcoAntoliniConvert conversation context into a Product Requirements Document and integrate it into an issue tracker.
