Peter Vu avatar

Peter Vu

Community

@pieberrykinnie · Winnipeg, MB, Canada

26Followers
|
112Public Repos
|
10Published Skills

Computer Science @ University of Manitoba

Skills Distribution
DomainDeveloper To...Specification-Driv.. (40%)Implementation Pla.. (30%)Requirements Clari.. (20%)GitHub Issue Manag.. (10%)

Agent Skills by Peter Vu

Showing 10 vetted skills indexed across 1 GitHub repositories.

Frequently Asked Questions About Peter Vu

FAQPage Schema
What tasks can I perform with pieberrykinnie's speckit skills?

You can create feature specifications from natural language, clarify underspecified requirements, generate implementation plans and dependency-ordered tasks, execute tasks against the codebase, run cross-artifact consistency analysis, build custom checklists, define project constitutions, and convert tasks into GitHub issues.

Who should use these speckit 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 that track implementation work through GitHub issues.

What is required to run these speckit skills?

Every skill requires an existing spec-kit project structure containing a .specify/ directory. Skills are user-invocable commands sourced from github-spec-kit templates, operating on spec.md, plan.md, and tasks.md artifacts within that project layout.

How do the speckit skills fit together in practice?

A typical sequence is: specify the feature, clarify ambiguities, generate a plan, produce tasks.md, analyze cross-artifact consistency, then implement. The converge skill appends unbuilt work as new tasks, and taskstoissues publishes remaining work as dependency-ordered GitHub issues.

Are these speckit skills open source?

The skills are authored by github-spec-kit and derived from its public templates/commands sources, distributed through pieberrykinnie's public GitHub registry. No licensing fee or commercial cost is indicated in the manifest; they are freely accessible user-invocable commands.