Tran Nguyen Tin
Community@eovipmak
Tran Nguyen Tin publishes GitHub spec-kit command skills enabling specification-driven development: feature specs, planning artifacts, task generation, and consistency analysis.
Agent Skills by Tran Nguyen Tin
Showing 10 vetted skills indexed across 1 GitHub repositories.
eovipmakspeckit-checklist
Generate requirements-quality checklists for spec-kit feature specifications.
eovipmakspeckit-constitution
Creates or updates the project constitution in a Spec Kit repository.
eovipmakspeckit-implement
Executes implementation plans by processing tasks defined in tasks.md.
eovipmakspeckit-converge
Assess codebase against spec, plan, and tasks, then append remaining work to tasks.md.
eovipmakspeckit-taskstoissues
Convert spec-kit tasks into deduplicated GitHub issues via the GitHub MCP server.
eovipmakspeckit-clarify
Identifies underspecified areas in feature specs and records targeted clarification answers.
eovipmakspeckit-plan
Generates implementation plans and design artifacts from feature specifications using a plan template.
eovipmakspeckit-analyze
Analyzes spec.md, plan.md, and tasks.md for cross-artifact consistency and coverage gaps.
eovipmakspeckit-specify
Generate a validated feature specification from a natural language feature description.
eovipmakspeckit-tasks
Generates a dependency-ordered tasks.md from spec-kit design artifacts.
Frequently Asked Questions About Tran Nguyen Tin
FAQPage SchemaWhat tasks can I perform using eovipmak's spec-kit skills?▼
You can create feature specifications from natural language, clarify underspecified requirements with targeted questions, generate implementation plans and dependency-ordered tasks, analyze cross-artifact consistency, convert tasks into GitHub issues, and execute implementation plans defined in tasks.md.
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, planning artifacts, and task breakdowns before writing code, plus teams tracking implementation work through GitHub issues.
What are the prerequisites for running these skills?▼
Every skill requires an existing spec-kit project structure containing a .specify/ directory. The skills operate on spec-kit artifacts such as spec.md, plan.md, and tasks.md, so the project must already be initialized with the github-spec-kit template layout.
How do the skills fit together in a development cycle?▼
Start with speckit-specify to draft the feature spec, refine it with speckit-clarify, build design artifacts via speckit-plan, generate tasks with speckit-tasks, validate with speckit-analyze, then execute via speckit-implement and close gaps using speckit-converge.
Are these skills free to use and who authored them?▼
The skills are published under the eovipmak registry by Tran Nguyen Tin, with metadata attributing authorship to github-spec-kit and sourcing from official templates/commands files. No licensing fees or paid tiers are indicated in the manifest.