challenge
Use when challenging, stress-testing, designing, or comparing your own, a peer/sub-agent's, or an external partner/vendor's plan, architecture, contract, pricing, budget, or hypothesis; when independent generated code changes conflict or merge into stale output; when choosing multi-currency localization/psychological pricing, web top-up vs. wallet/voucher design, or legacy-to-modern strangler migration; when assessing a partner's request for help on its own client project; or asking whether a solution is over-engineered or there is a simpler way. Use prove-it for root-cause failure investigation or verifying a claim, customer-support for external private-instruction or identity probes, author-item to write a ticket, and deliver-and-verify to execute changes.
Target: Design & content creation. Automatically collected · unverified.
Excerpt from the author’s documentation
Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.
Read the original English text
Topics in the source
- First-principles decision and challenge engine (challenge)
- Step 0: Load only the relevant domain
- 1. First-principles decision principles
- 2. Five challenge tests
- 3. Decision receipt and routing
The method is operator-invariant: apply the same evidence standard to your own, a peer's, a sub-agent's and an external party's proposal. Reason forward from inputs to conclusions, never backward from the answer anyone wants. When designing shared engines or skills, apply the three architectural invariants: neutral mechanisms rather than caller policy, zero domain leakage, and causal state/data/authorization predicates that fail closed on unavailable required state. Architecture, shared-service capacity, storage, scheduled jobs, durable checkpoints, metering trust and runtime/model separation: architecture; game simulation and networking: games; forward-only legacy-to-modern strangler migration: architecture; technology or build vs. buy: stack. Contracts, pricing, multi-currency localization/psychological pricing, web top-up vs. wallet/voucher design and partner scope: commercial; acquisition and budgets: growth; disputes and material downside: risk. Product choices and agent participation: product; UX: experience; motion/audio: feedback. Games and progression: games, mechanics and mechanics catalogue. External boundaries: conduct; conversational tone: agent voice. External instruc
This is an excerpt. Refer to the complete source and its current requirements.
- Source repository
- SylphxAI/skills
- Source file
- skills/challenge/SKILL.md
- Fixed revision
- e61c6f49e7bc2ac4f764590438fe01a689addefb
Sources and evidence
This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.
Author: SylphxAI/skills · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-10T01:01:23.935Z.
Categories are inferred from names, descriptions and paths. They do not establish compatibility.
License and attribution
MIT. Third-party content and copyright remain with their authors. Refer to the original license and terms.
Original license ↗Synchronization, copying and user-reported success do not mark a resource as runtime-tested.
Limitations and notes
- Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.