caldiaworks
- 23 skills
- 0 followers
- 6 hours ago last updated
- ▌ Deep Research · caldiaworksConduct deep research on any topic through structured investigation design. Use when the user needs comprehensive, multi-source analysis -- not a quick lookup. Triggers: deep research, comprehensive analysis, research report, compare X vs Y, analyze trends, investigate, or any request requiring synthesis across multiple perspectives. Do NOT use for simple questions answerable with 1-2 searches or for debugging.
- ▌ Skill Creator · caldiaworks bundleCreate new skills, improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, or benchmark skill performance with variance analysis.
- ▌ Divergence Loop · caldiaworks bundleContext-reset divergence brainstorming skill. Generates wild ideas through multiple rounds of context-isolated generation with extreme persona injection, then applies real-world constraints for structured convergence into multiple final ideas. Use when: brainstorm, diverge, divergence loop, idea generation, wild ideas, crazy ideas, generate ideas, brainstorming session, ideation divergence, think outside the box, or when the user wants to break out of conventional thinking patterns.
- ▌ Re Verify Logic · caldiaworksVerify logic diagrams against source code. Check line-number accuracy, Mermaid syntax, node completeness, and side effect documentation. Runs as independent Critic in fork context. Use when: verify logic, check logic diagram, validate phase 2, re-verify-logic.
- ▌ Re Verify Report · caldiaworksVerify consolidated As-Is specification for completeness, traceability, and accuracy. Cross-checks report against Phase 1-3 artifacts. Runs as independent Critic in fork context. Use when: verify report, check specification, validate phase 4, re-verify-report.
- ▌ Requirements DOCX · caldiaworks bundleConvert USDM/EARS requirements documents from Markdown to professionally formatted Word (.docx) files for client submission. Generates cover pages, table of contents, headers/footers, and styled requirement hierarchies. Leverages the docx skill for Word file generation. Use when: export requirements to Word, requirements to docx, USDM to Word, convert requirements document, 要件書をWord出力, 要件定義書のdocx変換, Word形式で要件書を作成, 要件定義書をWordに変換.
- ▌ Re Generate Report · caldiaworksAggregate reverse engineering artifacts into consolidated As-Is specification. Reads all phase outputs from manifest.json. Creates traceability matrix, cross-validates findings, and generates stakeholder-ready document. Use when: generate report, As-Is specification, consolidate analysis, final report, re-generate-report.
- ▌ Re Visualize Logic · caldiaworks bundleConvert source code into Mermaid flowcharts with line-number traceability. Reads targets from manifest.json (Phase 1 output). Visualizes control flow, data transformation, and side effects. Language-agnostic with optional language references. Use when: visualize logic, logic diagram, flowchart, control flow, re-visualize-logic.
- ▌ Skill Dev Workflow · caldiaworksOrchestrate the 9-step skill development lifecycle for the CaldiaWorks Skills repository. Guides through ideation, issue creation, planning, branch creation, requirements definition, skill implementation, commit, pull request, and post-merge issue cleanup. Use when: skill development workflow, develop a skill end-to-end, skill-dev-workflow, /skill-dev-workflow, create and publish a skill.
- ▌ Re Verify Structure · caldiaworksVerify structure analysis output against source code. Check file:line references, component completeness, and Mermaid diagram validity. Runs as independent Critic in fork context. Use when: verify structure, check structure map, validate phase 1, re-verify-structure.
- ▌ Re Structure Analysis · caldiaworks bundleAnalyze codebase structure for reverse engineering. Identify entry points, dependencies, modules, and components with file:line traceability. Creates manifest.json for pipeline chaining with Phase 2 (logic visualization). Language-agnostic with optional language reference files. Use when: reverse engineer, analyze structure, structure analysis, codebase analysis, re-structure-analysis.
- ▌ Re Verify Requirements · caldiaworksVerify extracted EARS requirements against source code. Check traceability, EARS classification accuracy, concrete value correctness, and completeness. Runs as independent Critic in fork context. Use when: verify requirements, check requirements, validate phase 3, re-verify-requirements.
- ▌ Re Extract Requirements · caldiaworks bundleExtract EARS requirements from source code and logic diagrams with Doer/Critic verification. Reads targets from manifest.json (Phase 2 output). Produces traceable requirements per component. Language-agnostic with optional language references. Use when: extract requirements, reverse engineer requirements, EARS extraction, re-extract-requirements.
- ▌ Ears · caldiaworks bundleWrite unambiguous specifications using EARS (Easy Approach to Requirements Syntax) patterns. Provides 6 sentence templates that eliminate ambiguity: Ubiquitous, Event-driven, State-driven, Unwanted behavior, Optional feature, and Complex. Use when: EARS, specification writing, write specs, 仕様を書く, EARS記法, 仕様を明確化, requirements specification, unambiguous specification.
- ▌ Usdm · caldiaworks bundleConvert ambiguous user requests into structured USDM requirements documents. Decomposes requirements into Requirement -> Reason -> Description -> Specification hierarchy. Integrates with GitHub Issues, Asana, and Jira tickets as input sources. Use when: create requirements, write requirements document, USDM, decompose requirements, requirements definition, 要件定義, 要件を整理, 要件分解.
- ▌ Commit · caldiaworksCreate focused git commits with change review, selective staging, and auto-drafted messages. Use when: commit, git commit, save changes, commit my work, make a commit, stage and commit, review changes before committing. Also use when the user says /commit or asks to commit specific files.
- ▌ Ideation · caldiaworks bundleTurn rough ideas into structured, validated idea documents through collaborative dialogue. Explores context, asks clarifying questions one at a time, proposes alternative approaches with feasibility evaluation, and produces documents ready for requirements definition. Use when: ideation, brainstorm, new idea, explore an idea, I want to build, what if we, let's think about, propose approaches, evaluate this idea, idea document, アイデア出し, 案出し, ブレスト, アイデアを整理, 検討したい.
- ▌ Planning · caldiaworksPlan work by analyzing GitHub Issues, identifying dependencies, proposing execution order, and defining work units that map to feature branches. Outputs a persistent plan document. Use when: plan work, planning, prioritize issues, organize issues, create a plan, work breakdown, define work units, what should I work on first, /planning.
- ▌ Discovery · caldiaworksInteractive wall-bouncing skill that transforms ambiguous user instructions into structured requirements memos through iterative 1-on-1 dialogue. Updates the requirements memo file every turn so the user can read it while conversing. Use when: discovery, wall-bounce, clarify requirements, ambiguous request, what do I need, help me think through, I have a vague idea, not sure what I want, requirements gathering, explore an idea, figure out what to build, or when the user starts with an unclear or underspecified request that needs structured exploration before any implementation.
- ▌ En Explainer · caldiaworks bundleExplain English technical documents and text in Japanese with contextual understanding. Not a simple translator -- reads the surrounding file or codebase context to provide deeper, more accurate explanations tailored for Japanese-speaking developers. Use when: explain this English, この英文を解説, 英語の解説, en-explainer, what does this mean, この英文の意味, 英文を日本語で説明, ドキュメントを解説, README解説, エラーメッセージの意味, コメントの意味, API仕様の解説, or when the user pastes English text and asks for explanation in Japanese. Also use when the user provides a file path and asks to explain specific English sections, or when they want to understand English code comments, error messages, config files, or technical documentation.
- ▌ Issue Create · caldiaworks bundleCreate GitHub Issues from user input or USDM requirements documents. Standalone mode guides through title, body, and labels. USDM mode creates a hierarchy of issues from requirements with specifications in the issue body. Use when: create issue, new issue, GitHub issue, open issue, file issue, create issues from requirements, USDM to issues, issue-create, /issue-create.
- ▌ Pull Request · caldiaworksCreate GitHub pull requests with readiness checks, auto-drafted titles and descriptions, and remote push handling. Use when: create PR, pull request, open PR, submit PR, create pull request, PR for review, push and PR, pull-request, /pull-request.
- ▌ Branch Create · caldiaworksCreate feature branches linked to issues with consistent naming conventions. Generates branch names from issue numbers and descriptions, creates the branch, and checks it out. Use when: create branch, new branch, feature branch, branch for issue, start working on issue, branch-create, /branch-create.