autodev-steering

Update project steering documents by comparing them with project data and GitHub issues.

5|Updated Mar 27, 2019
One-click install
npx skills add https://github.com/mizunashi-mana/blog --skill autodev-steering
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autodev-steering
Source: https://github.com/mizunashi-mana/blog/tree/main/.claude/skills/autodev-steering
Command: npx skills add https://github.com/mizunashi-mana/blog --skill autodev-steering

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of updating project steering documents, ensuring they accurately reflect the current project state and reducing the time spent on manual updates.

Core Features & Use Cases

  • Document Update Automation: Automatically update multiple steering documents (product, tech, plan, structure, etc.) to reflect the latest project state.
  • Issue Tracking Integration: Integrates with GitHub issues to ensure that open issues are accounted for in the documents.
  • Data Comparison: Compares existing documents with actual project data to identify outdated information.
  • User Confirmation: Allows users to review and confirm the updates before they are applied.
  • Use Case: After completing significant work on a project, use this Skill to update the project's steering documents to reflect the new information.

Quick Start

Run the autodev-steering skill to update all steering documents for the current project state.

Frequently Asked Questions about autodev-steering

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

FAQPage Schema
How do I automate project steering document updates with GitHub issues?

You can automate project steering document updates by comparing existing documents against actual project data and open GitHub issues to identify outdated information, then reviewing and confirming the changes before they are applied.

What is the best way to keep technical documentation current with project progress?

Keeping technical documentation current is achieved by automatically comparing steering documents like product and tech plans against actual project data, ensuring they accurately reflect the latest project state without manual effort.

Do I need shell commands to sync project documents with GitHub data?

Yes, syncing project documents with GitHub data requires shell commands for directory listing and GitHub API interaction to fetch actual project data and open issues for comparison against existing steering documents.

Can I review document updates before they are applied to my project?

Yes, the document update process includes a user confirmation step that allows you to review identified outdated information and confirm the proposed updates before any changes are applied to your steering documents.

What types of steering documents can be automatically updated for software development?

For software development projects, multiple steering documents including product, tech, plan, and structure documents can be automatically updated to reflect the latest project state based on actual project data and GitHub issues.

When should I run an automated update for project steering documents?

You should run an automated update for project steering documents after completing significant work on a project, ensuring that documentation accurately reflects new information and the current project state.