Magno Alves
Community@MagnoAlves1993
Magno Alves publishes GitHub spec-kit command skills enabling specification-driven feature development, from natural-language specs through planning, task generation, and implementation.
Agent Skills by Magno Alves
Showing 10 vetted skills indexed across 1 GitHub repositories.
speckit-checklist
Generate requirements-quality checklists for spec-kit feature specifications.
speckit-constitution
Creates or updates the project constitution from principle inputs using Spec Kit templates.
speckit-implement
Executes implementation plans by processing tasks defined in tasks.md.
speckit-converge
Assess codebase against spec, plan, and tasks, then append remaining work to tasks.md.
speckit-taskstoissues
Convert spec-kit tasks into dependency-ordered GitHub issues with deduplication.
speckit-clarify
Detects specification ambiguities and integrates targeted clarification answers into spec files.
speckit-plan
Generates implementation plans and design artifacts from feature specifications.
speckit-analyze
Analyzes spec.md, plan.md, and tasks.md for cross-artifact consistency and coverage gaps.
speckit-specify
Generates a validated feature specification from a natural language description using Spec Kit templates.
speckit-tasks
Generates a dependency-ordered tasks.md from spec-kit design artifacts.
Frequently Asked Questions About Magno Alves
FAQPage SchemaWhat tasks can I perform with Magno Alves's spec-kit skills?▼
You can create feature specifications from natural language, clarify underspecified requirements, generate implementation plans and design artifacts, produce dependency-ordered tasks.md files, execute implementations, analyze cross-artifact consistency, append unbuilt work via converge, and convert tasks into GitHub issues.
Who should use these spec-kit command skills?▼
Software engineers and technical leads practicing specification-driven development benefit most. They suit developers who want structured feature specs, implementation plans, and task breakdowns before writing code, plus teams needing GitHub issue generation from design artifacts.
What are the prerequisites for running these skills?▼
Every skill requires an existing spec-kit project structure containing a .specify/ directory. The skills originate from github-spec-kit templates (templates/commands/), so the project must be initialized with the spec-kit framework before any specify, plan, tasks, or implement command will function.
How do the skills fit together in a feature development lifecycle?▼
Start with speckit-constitution and speckit-specify to define principles and the feature spec, run speckit-clarify to resolve gaps, then speckit-plan and speckit-tasks to produce design artifacts and ordered tasks. Use speckit-analyze for consistency checks, speckit-implement to build, and speckit-converge to capture remaining work.
Are these spec-kit skills free to use?▼
The skills are published publicly under the MagnoAlves1993 GitHub account and are sourced from the github-spec-kit project's command templates. No licensing fee or paid tier is indicated in the manifest; they are derived from the open spec-kit template sources.