steering

Generate and update centralized steering documents and task lists across repositories.

Updated Jan 16, 2026
One-click install
npx skills add https://github.com/kumewata/dotfiles --skill steering-kumewata
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: steering
Source: https://github.com/kumewata/dotfiles/tree/main/config/agents/skills/steering
Command: npx skills add https://github.com/kumewata/dotfiles --skill steering-kumewata

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill records and tracks work plans and task lists by automatically generating a centralized steering document across the current project. It helps teams maintain a single source of truth for planning, execution, and retrospectives.

Core Features & Use Cases

  • Centralized documentation of task plans, task lists, and progress across the lifecycle of a project.
  • Triggered on user instructions to create, update, and review steering materials during planning, implementation, and verification phases.
  • Cross-repository coordination and unified visibility into workload and status.

Quick Start

Describe your task and the skill will generate a steering plan and update your task records.

Frequently Asked Questions about steering

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I centralize work plans and task lists across multiple repositories?

You can centralize work plans and task lists by triggering automated updates to tasklist.md, preserving progress in a central workspace at ~/.local/state/steering for unified cross-repository visibility.

What is a centralized steering document for project management?

A centralized steering document is a single source of truth that records and tracks task plans, implementation progress, and post-completion reviews across the entire project lifecycle.

How do I automatically update tasklist.md during project implementation?

You can automatically update tasklist.md by providing user instructions during planning, implementation, or verification phases, which triggers the skill to enforce updates to your task records.

Does centralized task tracking work for cross-repository coordination?

Yes, centralized task tracking supports cross-repository coordination by applying steering workflows across projects and preserving unified workload and status visibility in a central workspace.

What's the best way to maintain a single source of truth for project planning and retrospectives?

The best way to maintain a single source of truth is automating centralized documentation that records task plans and progress, applying it during planning, execution, and post-completion reviews.