Create specs and designs for a new change. Use this when you need to specify a new change or continue to work on the specification of an existing change.
Scanned 6/10/2026
Install via CLI
openskills install christianb93/WikiSpec---
name: wikispec-propose
description: Create specs and designs for a new change. Use this when you need to specify a new change or continue to work on the specification of an existing change.
---
# Skill: wikispec-propose
Drive the agent through the full `propose` step for a wikispec change. You will use the `wikispec` tool which is a binary in the path, no need to install anything.
## Steps
1. **Determine the change name.**
- If the user provided a change name, use it exactly.
- If no name was provided, but the user has provided a description of what to change, propose a short kebab-case name that captures the user's intent (e.g., `add-auth`, `fix-export-bug`)
- If no name is provided and no description is provided, assume that we will resume work on an existing active change. Use `wikispec list` to list all active changes. If there is only one name, assume that we will be working on this one, otherwise ask the user. Then skip step 2 (creation of the change) and proceed directly to step 3.
2. **Create the change.**
Run:
```
wikispec create --change <name>
```
- If the command succeeds, proceed to step 3.
- If the command fails because the change already exists, derive an alternative name (e.g., append `-2`) and retry this step.
3. **Gather context**
- load the `wikispec-wiki` skill to understand how to operate the knowledge wiki
- locate and read the wikis `index.md` file. Check whether any of the pages listed there are relevant for the functionality proposed by the user and read those pages.
- run `wikispec files --change <name>` to see whether there are already any specification files for this change, if yes read them
4. **Follow instructions in a loop.**
Repeat until the step is complete:
```
wikispec instructions --change <name> --step propose
```
- If the output contains instructions, follow them, then call the command again.
- If the output signals that the step is already complete, stop looping, inform the user that the propose step is complete and suggest to run `/wikispec-plan` next.
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.