- Home
- Skills
- Hellowind777
- Helloagents
- Templates
templates_skill
- Python
352
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill hellowind777/helloagents --skill templates- SKILL.md9.7 KB
Overview
This skill is a documentation template collection for creating project wikis and solution packages. It centralizes knowledge base templates, architecture and API docs, changelogs, and structured plan/history files to speed consistent documentation. Use it as the starting point for all project documentation and solution proposals.
How this skill works
The skill provides ready-to-fill markdown templates for changelogs, historical indexes, project overview, architecture, API manuals, data models, module pages, and solution planning files (why.md, how.md, task.md). Each template includes placeholder fields and clear section guidance so maintainers can copy, replace placeholders, and produce consistent output. It also includes version parsing rules that map common language ecosystems to primary and secondary version sources for automation and release workflows.
When to use it
- Creating or bootstrapping a project wiki or documentation site
- Preparing a formal change proposal or solution package for a feature
- Standardizing module-level or API documentation across teams
- Generating release notes and maintaining a changelog
- Defining technical designs, ADRs, and task lists for implementation
Best practices
- Replace all [...] placeholders with concrete content and dates before publishing
- Keep changelog entries minimal and follow semantic versioning
- Store ADRs and detailed technical rationale alongside feature histories
- Link module docs to main overview and history index for traceability
- Use the version parsing table to automate version discovery in CI
Example use cases
- Bootstrapping documentation for a new microservice with project.md, api.md, and data.md
- Authoring a change proposal (why.md) and technical design (how.md) for a large feature
- Creating a task.md checklist tied to requirement and scenario anchors for developer verification
- Maintaining a month-by-month history index and changelog for compliance and audits
- Configuring CI jobs to read version numbers using the provided parsing priority table
FAQ
They are structured and pragmatic but intentionally generic so teams can adapt conventions while ensuring traceability and consistency.
Can I automate generation from these templates?
Yes. Placeholders and consistent file names enable automation in CI to scaffold docs, generate release notes, and link history indices.