go-backend-dev-harness

Scan Go feature doc directories and write a reference section into tasks/todo.md.

Updated Aug 27, 2026

Search Tags:#automation #documentation #backend #reference #go #todo

Ready to run

npx skills add https://github.com/jssfy/k-skills --skill go-backend-dev-harness

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: go-backend-dev-harness
Source: https://github.com/jssfy/k-skills/tree/main/skills/development/go-backend-dev-harness
Command: npx skills add https://github.com/jssfy/k-skills --skill go-backend-dev-harness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the initialization and maintenance of feature documentation navigation by writing a centralized reference into tasks/todo.md.

Core Features & Use Cases

Scan the current feature document directory to enumerate plans, architectures, operation manuals, test records, and review notes.
Ensure a consistent, up-to-date reference section under tasks/todo.md for quick access during development and reviews.
Use Case: When starting a new backend feature, run this harness to create a single reference location summarizing all relevant docs.

Quick Start

Run this harness to scan the current feature document directory and populate tasks/todo.md with a references section.

Frequently Asked Questions about go-backend-dev-harness

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

FAQPage Schema

How do I initialize documentation navigation for Go backend features?▼

To initialize documentation navigation for Go backend features, run this harness to scan the feature document directory and write a centralized reference section into tasks/todo.md. It automatically enumerates plans, architectures, operation manuals, test records, and review notes for quick access.

What is the best way to maintain feature documentation references in a Go backend project?▼

The best way to maintain feature documentation references is to automate the process by scanning the current feature document directory. This ensures the reference section under tasks/todo.md is always present and up to date by enumerating all relevant architecture and test records.

How does scanning feature document directories work for backend plans and test records?▼

Scanning feature document directories works by traversing the current folder to discover and enumerate plans, architectures, operation manuals, test records, and review notes. It then aggregates these paths into a centralized reference section within tasks/todo.md.

Do I need external dependencies to automate Go backend documentation indexing?▼

No, you do not need external dependencies to automate Go backend documentation indexing. This harness requires no external dependencies beyond standard tooling to scan directories and populate tasks/todo.md with up-to-date references.

Can I use this automation for existing Go backend feature documents?▼

Yes, you can use this automation for existing Go backend feature documents. It applies to current feature document directories by scanning them to ensure a consistent, up-to-date reference section is generated under tasks/todo.md for development and reviews.