القائمة
Socratic method: expose false beliefs by disciplined questioning, not assertion.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Canonical b00t reviewer capability — adversarial multi-framework code/datum review. Shared across all harnesses (Claude Code, opencode, Hermes, b00t-cli). Loaded via: b00t learn reviewer, or by harness-specific role supplements.
Remove AI-generated artifacts from code. Three-phase certainty-graded cleanup. Use after any AI implementation session or before PR creation.
8-phase agile workflow — strategy→ideate→brainstorm→plan→work→review→compound→pulse. State machine with FOL-guarded transitions, gh-issues backlog, executable just harness. Inspired by everyinc/compound-engineering-plugin.
Australian crypto tax treatment per ATO guidance QC 53725. Crypto assets are CGT assets under ITAA 1997 s 108-5. Each disposal triggers CGT event A1. Covers personal-use exception, trading stock test, and the 50% CGT discount.
Australian R&D Tax Incentive (RDTI) — ITAA 1997 Division 355. Covers eligibility criteria for core and supporting R&D activities, registration with AusIndustry/IP Australia, expenditure categories, offset rates, and the company size threshold test.
Evidence graph construction for tax audit trails. Each Satisfies check emits EvidenceNode structs with Blake3 content hashes. Evidence chains are tamper-evident and link legislative citations to factual findings.
| name | socratic |
| type | skill |
| hint | Socratic method — question assumptions systematically; ask 'why?' before accepting any premise |
| version | 1.0.0 |
| tags | ["transferable","socratic","questions","assumptions","dialectic","inquiry","challenge","premise","why"] |
| tier | sm0l |
| complexity | 3 |
| description | Socratic method: expose false beliefs by disciplined questioning, not assertion. |
The Socratic method exposes false beliefs through disciplined questioning rather than assertion. Never accept a premise at face value — probe it: "What do you mean by X?" "How do you know that?" "What is the evidence?" "What are the counter-examples?" "What follows if you're wrong?" Apply this to your own reasoning too — an internal Socratic dialogue catches errors before they ship.
In code review, ask "why is this abstraction here?" not "this abstraction is wrong." The goal is not to win — it is to find the true answer through collaborative inquiry. The elenchus technique leads the speaker to contradict themselves, exposing hidden assumptions.
Use the Socratic method whenever you encounter an accepted premise that deserves scrutiny: during code review, requirements gathering, debugging, architecture decisions, or whenever someone says "that's how it's always been done."
