Skill UI

This skill helps transform vague product or engineering ideas into structured, verifiable acceptance criteria (AC). It is crucial for high-impact changes involving security, data migration, or external APIs. By inspecting existing context and asking minimal, targeted questions, it produces clear, observable criteria, significantly de-risking the development process and ensuring handoff readiness.

This guide assists in building robust, mechanism-driven theories for academic manuscripts, particularly in organizational science. It teaches the critical distinction between process theories (explaining how and why things unfold) and variance theories (explaining how much things vary). It emphasizes defining generative mechanisms, specifying boundary conditions, and structuring arguments for both inductive and deductive research designs, ensuring the theory is the core contribution.

This guide provides a rigorous framework for developing robust, theory-driven hypotheses in accounting research, especially for high-impact academic journals. It teaches researchers how to transition from observing mere correlations to formulating hypotheses grounded in established economic theories, such as agency theory, information economics, and positive accounting theory. The process emphasizes identifying the core economic friction, naming the acting agents and their incentives, and deriving directional, falsifiable, and a priori predictions.

A guide for developing robust, theory-driven hypotheses for top-tier international business journals (e.g., JIBS). It focuses on specifying cross-level logic (country/culture $\rightarrow$ firm/individual), identifying boundary conditions, and grounding arguments in established IB theoretical traditions. It teaches how to move beyond merely running data in a foreign context to making the international environment itself a causal variable.

This comprehensive guide helps researchers move beyond descriptive correlations to build rigorous, theory-driven manuscripts for top-tier IS journals. It outlines how to structure theoretical arguments based on specific research styles, including IT business value mechanisms, platform economics, behavioral models, and economic incentives, emphasizing the derivation of hypotheses and comparative statics before empirical testing.

A comprehensive guide for academic writers in demography and development studies. It teaches authors how to transform technical, results-heavy manuscripts into lucid, essayistic, and argument-driven narratives. Focuses on linking population quantities to their broad development and policy implications, ensuring readability for diverse non-specialist academic audiences and adhering to specific journal house conventions.

A hands-on interactive tutorial that teaches Ouroboros, a specification-driven development tool. Guides users from vague ideas to precise Seeds through Socratic interviews and a clear workflow, with practical commands and audience-adapted pacing.

Archives a Specification-Driven Development (SDD) change by syncing delta specs into the main specs and moving the change folder to the archive, completing the SDD cycle. Handles artifact store modes (engram, openspec, hybrid, none) and produces a terminal archive report with final-state authority.

Guides users through a complete Spec-Driven Development (SDD) cycle on their actual codebase, from exploration to archive. Interactive walkthrough with narrated phases, teaching by doing. Suitable for onboarding developers to SDD methodology.

Sub-agent for Specification-Driven Development (SDD) research. Investigates optional questions using authorized external sources, returns evidence, gaps, and recommendations to the orchestrator.

Run optional practical diagnostics against available implementation and artifacts within Spec-Driven Development. Inspect code, run tests, build and type checks, and report findings, limitations, and next steps without mutating code.

This skill executes tasks from a project's implementation plan following Test-Driven Development (TDD) workflows. It manages track selection, loads necessary context, guides coding through Red-Green-Refactor phases, handles commits, and verifies phase completion. Use it when working on specific implementation tracks or needing guidance on best practices for structured development.