wiki-init
wiki-init
Use this skill to initialize or migrate a repo into the wiki + QMD + agent hook pattern.
The user may use natural language. Route intent like this:
- "como esta a estrutura?", "preciso migrar?", "doctor", "qmd esta ok?" -> run
doctor. - "instala", "prepara esse repo", "configura hooks" -> run
installas dry-run first, then ask the user to confirm the suggested wiki location and index before--write. - "migrar para o formato novo" -> run
migrateas dry-run first, then ask the user to confirm the suggested wiki location and index before--write. - "corrigir qmd", "managed qmd", "patch qmd" -> run
doctor, then useinstall --writeorupdate-hooks --writewith explicit approval to prepare the managed QMD checkout and wrappers.
Workflow
- Run
scripts/wiki-init.ts doctor --project <path>first. - Read the report: wiki layout, AGENTS/CLAUDE, harnesses, hooks, drift, QMD status.
- For changes, run
installormigratewithout--writeand show the planned file actions plus the suggested topology. - Ask the user in plain language to confirm where the wiki will live and what QMD index will be used. Do not require the user to know the preset name.
- Only run with
--writeafter passing explicit--wikiand--index. The script blocks writes without those flags. - Re-run
doctorafter writes.
More from djalmajr/essential-skills
agile-proto
Create interactive UI prototypes with a CDN-only stack (z-proto + Tailwind v4 + shadcn-style components + Preact/htm + preact-iso), including faithful send-to-Figma captures when requested. Use when asked to "prototype", "create proto", "mockup screens", "interactive prototype", "send to Figma", or when exploring UI flows before implementation.
18agile-metrics
Consolidates objective metrics of a sprint. Use when you need quantitative data about deliveries, blockers, deviations, and velocity to feed retro, sprint review, or capacity decisions.
17agile-retro
Conducts retrospective with learnings and improvement actions. Use when a cycle, sprint, or delivery has ended and the team needs to reflect on what worked and what needs to change. Also absorbs post-implementation reflection aspects.
16agile-intake
Structures new and vague problems into clear intake documents. Use when the problem is not yet mature enough for the backlog, when someone brings an idea or need without defined scope, or when you need to decide what the next artifact in the flow should be.
16agile-roadmap
Maps multi-phase trajectories with dependencies into clear, sequenced roadmaps. Use when work has multiple phases that need sequencing, when decisions today affect future decisions, when stakeholders need to see the whole journey, or when external dependencies exist. Applicable regardless of total duration — a 4-week multi-phase initiative benefits as much as a quarterly roadmap.
16agile-epic
Structures large initiatives into a decomposed backlog with roadmap, dependencies, and verification. Generates an overview file plus individual story files with tasks. Use when work requires several coordinated stories, has dependencies between deliveries, or needs a roadmap.
16