Audit and update specification files in the specs/ directory.
npx skills add https://github.com/softwareByAndi/workflow --skill manage-specs
Please help me install this Agent Skill. Skill: manage-specs Source: https://github.com/softwareByAndi/workflow/tree/main/.claude/skills/manage-specs Command: npx skills add https://github.com/softwareByAndi/workflow --skill manage-specs
This Skill ensures that the project's specification files (specs/) are accurate, up-to-date, and well-organized, reflecting the current state of the source code and project architecture.
Run the manage-specs skill to perform a full audit of all spec files.
High-intent search queries and answers about installing and using this skill.
To audit spec files and prevent documentation drift, compare your `specs/` directory against recent changes in `src/` and `resources/` source files. This process identifies outdated specifications by mapping source file modifications to their corresponding documentation.
The best way to maintain specification files is to run an automated audit that enforces a strict frontmatter schema and Markdown body format. This ensures all documents in the `specs/` directory accurately reflect the current source code architecture.
To create new specs that map to your source files, scaffold specification documents by mapping source files to their architectural purposes. This enforces a strict frontmatter schema and Markdown body format for all new subsystem documentation.
Yes, you need npm installed to run manage-specs for code audits. npm is a required dependency to execute the scripts that identify stale specifications and maintain the specification directory structure.
Your spec file audit fails because all specification documents must adhere to a strict frontmatter schema and Markdown body format. Deviations from this enforced structure within the `specs/` directory will trigger validation errors during the code audit.
Yes, you can restructure the spec tree hierarchy for a large project architecture. The skill helps maintain a logical document structure within the `specs/` directory by organizing specifications according to source file relationships.
az9713Initialize a project with dark code prevention directories, CLAUDE.md section, and baseline audit.
liza-masReconstruct MADR-formatted Architecture Decision Records from commits and documentation.
phoenixvcAutomate compilation, testing, and deployment of software projects.
zzafergokConvert Markdown documents to HTML using marked.js, pandoc, gomarkdown, or static site generators.
