plan-authoring-cycle
HAIOS Plan Authoring Cycle for structured plan population. Use when filling in implementation plan sections. Guides AMBIGUITY->ANALYZE->AUTHOR->VALIDATE workflow.
Explore AI skills for development, content, data and productivity. Compare the description and repository popularity before opening a skill.
HAIOS Plan Authoring Cycle for structured plan population. Use when filling in implementation plan sections. Guides AMBIGUITY->ANALYZE->AUTHOR->VALIDATE workflow.
HAIOS Memory Agent for intelligent context retrieval and learning. Use BEFORE answering complex questions to retrieve relevant strategies and context. Use AFTER completing tasks to extract and store learnings....
4 questions for genuine reflection before work closure. Hard gate on non-empty.
Create checkpoint manifest. Scaffold, populate fields, commit.
HAIOS Observation Triage Cycle for processing captured observations. Use when scanning archived work items to triage and act on observations. Guides SCAN->TRIAGE->PROMOTE workflow with dimension validation.
HAIOS Survey Cycle for structured session-level work selection. Use after coldstart context loading. Guides GATHER->ASSESS->OPTIONS->CHOOSE->ROUTE workflow with volumous exploration before tight commitment.
HAIOS Investigation Cycle for structured research and discovery. Use when starting or resuming an investigation. Guides HYPOTHESIZE->EXPLORE->CONCLUDE workflow with phase-specific tooling.
Persistent memory and context compression for Claude Code. Use when setting up or operating MemoryLane in a project, recalling or storing memories, reviewing insights, curating low-quality memories, or checking...
Zero-config persistent memory for Claude with automatic cost savings. Use when you need to remember project context, reduce API token costs, track learned patterns, manage memories across sessions, or curate/cl...
Git merge workflow using --no-ff flag with rebase-first strategy for clean history. Use when project's CLAUDE.md or documentation specifies this merge workflow, when merging feature branches, or when asked to f...
Generate tags for a blog post.
Erstellt deployment-ready Publication Package mit Next.js Code, Metadata und Schemas. Phase 7 des SEO Workflows.
Orchestriert komplette 7-Phase SEO Pipeline von Keyword Research bis Publication. Verwenden bei "SEO content erstellen" oder "neuen ratgeber artikel".
Verarbeitet Bilder für PferdeWert - konvertiert zu WebP mit sprechendem Namen. Automatisch verwenden wenn User einen Bild-Link schickt!
Erstellt produktionsreife Frontend-Komponenten mit dem PferdeWert Design-System. Automatisch verwenden bei UI-Entwicklung, Styling, Component-Erstellung.
Validiert Content-Qualität, E-E-A-T Signals und Brand Compliance. Quality Gate vor Publication. Verwenden bei "qualität prüfen" oder "content validieren".
Lektoriert deutschen SEO-Content für natürlichen Sprachfluss und hohen Readability-Score. Korrigiert Keyword-Stuffing, Grammatikfehler und unnatürliche Konstruktionen. Verwenden bei "lektorieren", "deutsch prüf...
Erstellt aus SEO-Content automatisch fertige Ratgeber-Seiten. Verwenden wenn User "ratgeber erstellen" oder "page aus SEO content" sagt.
Erstellt SEO Metadata, Structured Data Schemas und Internal Linking Empfehlungen. Verwenden bei "schema erstellen" oder "metadata optimieren".
Analysiert und optimiert bestehende Ratgeber-Artikel durch DataForSEO-Analyse mit automatischer Implementierung. Verwenden bei "artikel optimieren" oder "ranking verbessern".
Auto-review Go code for 100+ common mistakes when analyzing .go files, discussing Go patterns, or reviewing PRs with Go code. Checks error handling, concurrency, interfaces, performance, testing, and stdlib usa...
Creates structured development plans with phases, subtasks, and progress tracking using markdown files in .llms/ directory. Use when starting new features or complex tasks that need planning.
Executes development plans from .llms/ directory phase by phase, updating progress, managing git commits, and handling validation cycles. Use to work through existing development plans.
Orchestrates complex or architectural code changes through a structured workflow. Use when the user requests multi-file changes, new features, architectural refactoring, database schema changes, new API endpoin...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.