fp-implement

You can manage the task pipeline by claiming issues, moving them to in-progress, and adding progress comments. This skill automates that workflow while enforcing structured metadata and contextual logging for software development teams.

Managing task dependencies in an agile workflow involves viewing task hierarchies to understand relationships before claiming work. This skill supports breaking down large tasks into sub-tasks and tracking related dependencies across todo, in-progress, and done states.

The fp workflow is an end-to-end issue management process for software teams. It enforces structured metadata via YAML frontmatter, tracks tasks across todo, in-progress, and done states, and evaluates issue content for toxicity.

Yes, you can enforce structured metadata on issue tickets. This skill requires YAML frontmatter with name and description fields, defined sections, and metadata such as dependencies and components to maintain project accountability.

Yes, this issue management workflow supports breaking down large tasks into sub-tasks. You can view task hierarchies, manage related dependencies, and log frequent progress updates to maintain context across the development lifecycle.

You should use a structured issue pipeline when your software team needs to coordinate effort, maintain context, and track progress with accountability. It enforces repeatable workflows from discovery through completion, which basic task tracking lacks.