Wikispec Propose
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.
Install
$ agentstack add skill-christianb93-wikispec-wikispec-propose ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-christianb93-wikispec-wikispec-propose) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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
- 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 listto 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.
- Create the change.
Run: `` wikispec create --change ``
- 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.
- Gather context
- load the
wikispec-wikiskill to understand how to operate the knowledge wiki - locate and read the wikis
index.mdfile. Check whether any of the pages listed there are relevant for the functionality proposed by the user and read those pages. - run
wikispec files --changeto see whether there are already any specification files for this change, if yes read them
- Follow instructions in a loop.
Repeat until the step is complete: `` wikispec instructions --change --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-plannext.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: christianb93
- Source: christianb93/WikiSpec
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.