Konstantinos Malavazos
Community@konstantinos-malavazos
Konstantinos Malavazos maintains a 22-skill registry for orchestrating multi-session software delivery: charting, spec decomposition, TDD, diagnosis, memory governance, and repo scaffolding.
Agent Skills by Konstantinos Malavazos
Showing 22 vetted skills indexed across 1 GitHub repositories.
memory-schema
Enforces correct memory server tool call shapes, required fields, enums, and character caps before memory writes.
research
Investigate external documentation and vendor APIs, then capture cited findings as Markdown files.
pitch
Evaluates raw product ideas through a six-question kill gate producing build, kill, or park verdicts.
adapt-to-stack
Generate layer specialist agents and standards skills from a repo's CLAUDE.md chain declaration.
bootstrap
Scaffold an empty decided repo and verify pipeline preconditions with a checked report.
wait-what
Re-explains the last message using simplified English and established project vocabulary.
<layer>-engineering-standards
Generates per-layer coding and review standards scoped to a single language or stack layer.
handoff
Writes a session handoff document that a fresh conversation can resume work from.
to-tickets
Splits a slice-ready spec into independent vertical-slice work-units with a dependency board.
wizard
Generate interactive bash wizards that walk humans through manual setup procedures.
to-questionnaire
Generates a structured Markdown questionnaire to extract answers from a specific person.
to-spec
Converts an approved planner.md into a slice-ready spec with testing seams and behaviour boundaries.
prototype
Build throwaway code prototypes that answer design questions through human reaction.
diagnose
Diagnose bugs and performance regressions through a disciplined reproduce-and-measure loop.
commit-conventions
Enforces type/scope/ticket-id commit message and branch naming conventions with one-commit-per-branch amend workflow.
charting
Plan multi-session efforts by mapping decisions and tasks as tickets on an issue tracker.
dispatch-weight
Classifies each implementation dispatch as light or heavy to guide per-run model escalation.
next-steps
Generates a four-field closing block stating what landed, user actions, and the next command.
memory-tag-lint
Validates candidate memory tags against seven assertions before writing them to the vocabulary cache.
tdd
Guides test-driven development using the red-green-refactor loop for features and bug fixes.
grilling
Stress-test plans by interviewing users to resolve or defer every open decision.
cut-backlog
Converts a closed charting map into an ordered, dependency-tracked ticket backlog.
Frequently Asked Questions About Konstantinos Malavazos
FAQPage SchemaWhat tasks can I accomplish with Konstantinos Malavazos's skill registry?▼
You can chart vague large efforts into tracker tickets, bootstrap empty repos with layer specialists, split specs into vertical slices, run TDD and structured bug diagnosis, validate ideas through a one-hour kill gate, and manage session handoffs and memory writes with enforced schemas.
Who is the target user for these skills?▼
Software engineers and technical leads running agent-assisted development across many sessions. It suits people managing large tickets, multi-layer repos with CLAUDE.md chains, and teams needing commit conventions, backlog cutting, and deferred-decision grilling before implementation.
How do the skills fit together in practice?▼
They form a pipeline: pitch or chart an idea, bootstrap the repo, decompose specs into slice tickets via to-spec and to-tickets, implement with TDD and dispatch-weight model escalation, then close with handoff and next-steps blocks so a fresh session resumes cleanly.
What prerequisites or dependencies do these skills require?▼
Skills expect a workspace with a .claude directory, a repo CLAUDE.md declaring a layer chain for adapt-to-stack, an issue tracker for charting and cut-backlog, and a memory server whose write schema memory-schema and memory-tag-lint enforce. Several skills are disable-model-invocation and run only on explicit user command.
Are these skills open source and what do they cost?▼
The manifest states no license or pricing information. The skills are plain frontmatter-described definitions in a public GitHub registry under konstantinos-malavazos; users should check the repository directly for licensing terms before reuse.