challenge
Pre-mortem plan analysis. Imagine the plan failed 12 months from now and work backwards to find the weaknesses. Surfaces assumptions, dependencies, and execution risks before committing resources. Use when before significant resource commitment, before presenting to a board or investors, when feedback has been one-sidedly positive, or when there is pressure to move fast and figure it out later.
Governance Receipt
- Signer
- sovereign-claw-ed25519
- Signed At
- 6/4/2026
- Risk Tier
- T0
- Receipt Hash
- aaabddb6
- Manifest Hash
- e77d7626cdb5e53c1f5a4e8ad8fe8c2861d6aea64a2962d2bebb9dfb5fa85443
- Signature
- o6TlbChI
- Root Public Key
- 349b0348
Skill Details
- Gate Verdict
- Attested
- Publication State
- published
- Risk Tier
- T0
- Manifest Hash
- e77d7626
Download Attested Bundle
Install challenge
Each bundle is served from the attested copy of challenge, so the file you download is the one covered by the governance receipt on this page rather than whatever currently sits at the upstream source.
Claude Code skill
curl -L "https://atestiv.com/api/download/challenge?format=claude-code" -o challenge.skill.mdMCP tool definitions
curl -L "https://atestiv.com/api/download/challenge?format=mcp" -o challenge.mcp-tools.jsonRaw attested bundle
curl -L "https://atestiv.com/api/download/challenge?format=raw" -o challenge.bundle.jsonVerify the bundle against its manifest hash
shasum -a 256 challenge.bundle.jsonProvenance
- Catalog identifier:
challenge - Harvested from the upstream repository.
- The manifest hash below is what the signing key committed to. A bundle whose digest does not match it is not the attested challenge.
- Anything published here has been through the same gate, so a missing receipt is itself a signal rather than an omission.
More Skills
change-management
Framework for rolling out organizational changes without chaos. Covers the ADKAR model adapted for startups, communication templates, resistance patterns, and change fatigue management. Handles process changes, org restructures, strategy pivots, and culture changes. Use when announcing a reorg, switching tools, pivoting strategy, killing a product, changing leadership, or when user mentions change management, change rollout, managing resistance, org change, reorg, or pivot communication.
changelog
Generate changelogs from git history and validate conventional commits. Usage: /changelog <generate|lint> [options]
Changelog Generator
Generates changelogs from git history using conventional commits. Covers semantic versioning, breaking change detection, and release note formatting.