Generate template-driven feature documentation with frontmatter metadata.
npx skills add https://github.com/alunadev/ald_skills --skill feature-documenter
Please help me install this Agent Skill. Skill: feature-documenter Source: https://github.com/alunadev/ald_skills/tree/main/workflows/feature-documenter Command: npx skills add https://github.com/alunadev/ald_skills --skill feature-documenter
Use PROACTIVELY to document new features, significant code changes, or when creating technical specifications for a feature not included in the original project technical specification. Specializes in creating comprehensive feature documentation for non-professional developers.
To generate documentation for a new feature, invoke the feature-documenter on the feature draft and provide key details such as purpose, scope, and acceptance criteria.
High-intent search queries and answers about installing and using this skill.
Write feature documentation for non-professional developers by using a template-driven approach that establishes clear, reusable specifications. This ensures new functionality is documented proactively with structured metadata for planning and QA.
Proactive feature documentation is the process of creating technical specifications before coding begins. You need it when adding new features, making significant code changes, or defining requirements not included in the original project specification.
Create reusable technical specifications by enforcing structure through standardized templates and frontmatter metadata. This generates comprehensive feature documentation that provides guidance for contributors across product teams.
Yes, you can use template-driven documentation to generate consistent feature docs suitable for product teams, engineers, and technical writers. The output establishes clear specifications for planning, development, and QA.
The best way to document significant code changes for stakeholders is to use standardized templates that produce collaboration-ready docs. This articulates requirements clearly and ensures comprehensive coverage of the functionality.
Yes, feature documentation works without a detailed technical specification by guiding teams to articulate requirements proactively. It specializes in creating comprehensive feature docs for features not included in the original project specification.
asalhamedDraft PRDs and acceptance criteria from stakeholder inputs using MoSCoW and RICE frameworks.
RedBoardDevConvert feature ideas and documentation into detailed development plans.
o2b3kExecute sequential implementation tasks from a markdown plan file with persistent state tracking.
OpenLaborWrite technical specifications covering design, rollout, and open questions.
