B18Bu avatar

B18Bu

Community

@B18Bu

0Followers
|
5Public Repos
|
10Published Skills

B18Bu provides spec-kit command skills for specification-driven development, covering feature specs, planning, task generation, analysis, and GitHub issue conversion.

Skills Distribution
DomainDeveloper To...Specification Auth.. (30%)Implementation Pla.. (30%)Codebase Consisten.. (20%)GitHub Issue Manag.. (10%)

Agent Skills by B18Bu

Showing 10 vetted skills indexed across 1 GitHub repositories.

Frequently Asked Questions About B18Bu

FAQPage Schema
What tasks can I accomplish with B18Bu's spec-kit skills?▼

You can create feature specifications from natural language, clarify ambiguous requirements, generate implementation plans and dependency-ordered tasks.md files, execute tasks, analyze cross-artifact consistency, assess codebase convergence against specs, build custom checklists, 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 maintain structured spec.md, plan.md, and tasks.md artifacts and want consistent, auditable progression from feature description through planning, task execution, and issue tracking.

What are the prerequisites for running these 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, so the project must already be initialized with the spec-kit layout before invoking specify, plan, tasks, analyze, or related commands.

How do the skills fit together in a typical development sequence?▼

Start with speckit-constitution and speckit-specify, refine with speckit-clarify, then run speckit-plan and speckit-tasks. Validate with speckit-analyze and speckit-checklist, execute via speckit-implement, close gaps with speckit-converge, and publish remaining work using speckit-taskstoissues.

Are B18Bu's spec-kit skills free to use?▼

The skills are derived from github-spec-kit command templates and carry no stated licensing fee in the manifest. They are user-invocable within a compatible spec-kit project, with model invocation enabled, so usage cost depends only on the host environment running them.