Mario Norato
Community@marionoratoRN
Mario Norato maintains a spec-kit command suite for specification-driven feature development, covering specification, planning, task generation, analysis, and GitHub issue conversion.
Agent Skills by Mario Norato
Showing 11 vetted skills indexed across 1 GitHub repositories.
marionoratoRNspeckit-checklist
Generate requirements-quality checklists for feature specifications in spec-kit projects.
marionoratoRNspeckit-constitution
Creates or updates the project constitution file from provided governance principles.
marionoratoRNspeckit-implement
Executes implementation plans by processing tasks defined in tasks.md.
marionoratoRNspeckit-converge
Assess codebase against spec, plan, and tasks, then append remaining work to tasks.md.
marionoratoRNspeckit-taskstoissues
Convert spec-kit tasks into dependency-ordered GitHub issues with deduplication.
marionoratoRNspeckit-clarify
Identifies ambiguities in feature specifications and integrates clarification answers into spec files.
marionoratoRNspeckit-plan
Generates implementation plans and design artifacts from feature specifications in spec-kit projects.
marionoratoRNspeckit-workflow
Guides feature development through the eight-step spec-kit workflow from specification to audited implementation.
marionoratoRNspeckit-analyze
Analyze spec.md, plan.md, and tasks.md for cross-artifact consistency and coverage gaps.
marionoratoRNspeckit-specify
Generates a validated feature specification from a natural language feature description.
marionoratoRNspeckit-tasks
Generates a dependency-ordered tasks.md checklist from spec-kit design artifacts.
Frequently Asked Questions About Mario Norato
FAQPage SchemaWhat tasks can I perform with Mario Norato's spec-kit skills?▼
You can create feature specifications from natural language, clarify ambiguous requirements, generate implementation plans and dependency-ordered tasks, execute those tasks, run cross-artifact consistency analysis, build requirement checklists, define project constitutions, and convert tasks into GitHub issues.
Who should use these spec-kit skills?▼
Software engineers and technical leads practicing specification-driven development benefit most. They suit teams that want structured feature specs, planning artifacts, and task breakdowns before writing code, plus maintainers who want specs, plans, and tasks kept consistent.
What are the prerequisites for running these skills?▼
Each skill requires an existing spec-kit project structure containing a .specify/ directory. The commands operate on spec-kit artifacts such as spec.md, plan.md, and tasks.md, so the project must already be initialized with the spec-kit template layout.
How do the spec-kit skills fit together in practice?▼
A typical sequence is: specify the feature, clarify underspecified areas, generate a plan, produce tasks.md, analyze cross-artifact consistency, then implement the tasks. The converge skill appends remaining unbuilt work as new tasks, and taskstoissues publishes them as GitHub issues.
Are these spec-kit skills free to use?▼
The skills originate from github-spec-kit templates (templates/commands/) and are published in a public GitHub repository by Mario Norato. No licensing fee or paid tier is indicated in the manifest; they are distributed as open template-based command definitions.