Lateef Alabi-Oki
Community@mystilleef · USA
Lateef Alabi-Oki maintains a skill registry for structured software engineering: SPAE spec-plan-build-verify lifecycle, code review, refactoring, testing, and atomic git commits.
Agent Skills by Lateef Alabi-Oki
Showing 23 vetted skills indexed across 2 GitHub repositories.
mystilleefrun
Executes named subagent roles with optimized task instructions via explicit invocation.
mystilleeftroubleshoot
Diagnose failures through hypothesis-driven testing, root-cause fixes, and verification loops.
mystilleefauto-commit
Groups repository changes into atomic commits with conventional commit messages and secret scanning.
mystilleefpurify
Remove dead code, redundant abstractions, and hygiene violations while preserving intended behavior.
mystilleefspae-build
Executes one atomic task from PLAN.md with test-driven implementation and state persistence.
mystilleefcode-review
Review diffs, commits, and PRs to detect defects with severity-ranked findings.
mystilleefdocument
Write and update caller-facing documentation for code APIs, modules, and behavior.
mystilleefspae-spawn
Orchestrates build, check, and fix subagents in a loop driven by STATE.json phase transitions.
mystilleefspae-check
Verifies active task implementation against PLAN.md acceptance criteria and routes gaps to fix.
mystilleefspae-inspect
Performs gap analysis on PLAN.md against SPEC.md and codebase constraints before task execution.
mystilleefspae-spec
Generates SPEC.md and STATE.json files from proposals for the SPAE structured workflow.
mystilleefclean
Orchestrates purify and refactor subagents sequentially to clean target code.
mystilleeftip
Generates a life perspective shift and a productivity tip as concise markdown text.
mystilleefspae-prepare
Orchestrates spec, plan, and inspect subagents sequentially through the SPAE workflow phases.
mystilleefspae-plan
Decomposes SPEC.md requirements into an atomic, acyclic task graph in PLAN.md.
mystilleefspae-fix
Remediates pre-classified task gaps from FIX.md using test-driven minimal changes.
mystilleefspae-verify
Verifies implemented code against SPEC.md requirements and issues pass, fail, or blocked verdicts.
mystilleefrefactor
Refactor code to fix DRY, SOLID, and structure violations while preserving behavior.
mystilleefspae-orchestrate
Orchestrates SPAE subagents sequentially through a state-driven seven-phase workflow.
mystilleefreview-mode
Analyze roadmaps, code, and strategies to identify flaws and risks.
mystilleefwrite-mode
Remove the .gemini_readonly marker to enable write mode after user authorization.
mystilleefimplement-mode
Execute approved roadmaps with verification-first implementation and detailed session summaries.
mystilleefreadonly-mode
Create a persistent marker file and run a shell script to enable read-only mode.
Frequently Asked Questions About Lateef Alabi-Oki
FAQPage SchemaWhat tasks can I perform with mystilleef's skills?▼
You can run the full SPAE lifecycle (spec, plan, inspect, build, check, fix, verify), review code for bugs, write gap-covering tests, refactor DRY/SOLID violations, purify KISS/YAGNI issues, document APIs, troubleshoot systematically, and auto-commit changes atomically.
Who are these skills designed for?▼
Software engineers and maintainers who want disciplined, verification-first development. The skills suit developers managing structured proposals via SPEC.md and PLAN.md, enforcing code quality gates, and delegating review, testing, and remediation to named agent roles.
How do I invoke and run these skills in practice?▼
User-invocable skills are triggered explicitly with slash commands like /spae-spec, /spae-plan, /test, /refactor, or /troubleshoot, often accepting an optional file path or focus area. Non-invocable orchestrators like spae-orchestrate, clean, and coverage run subagents sequentially.
What are the prerequisites for the SPAE skills?▼
SPAE skills expect a repository containing SPEC.md and PLAN.md artifacts. spae-spec generates the spec and state file from a proposal, spae-plan decomposes SPEC.md into a task DAG, and spae-fix requires FIX.md written by a prior /spae-check run.
How do read-only and write modes work?▼
readonly-mode creates a persistent .gemini_readonly marker file via a shell script to restrict changes. write-mode removes that marker only after explicit user authorization, gating implement-mode's roadmap execution behind an approval step.