yujikawa
Community@yujikawa · Fukuoka Japan
I work as an analytics engineer in Japan.
Agent Skills by yujikawa
Showing 21 vetted skills indexed across 1 GitHub repositories.
yujikawaopenspec-apply-change
Implements tasks from an OpenSpec change using the openspec CLI.
yujikawaopenspec-explore
Explores ideas, investigates codebases, and clarifies requirements through conversational analysis.
yujikawaopenspec-archive-change
Archives completed OpenSpec changes with artifact, task, and spec sync verification.
yujikawaopenspec-propose
Generates complete change proposals with design, specs, and tasks via the openspec CLI.
yujikawamodscape-spec-note
Appends free-form knowledge notes to permanent table spec markdown files.
yujikawamodscape-spec-explore
Explores data model schemas and clarifies change direction before formal requirements gathering.
yujikawamodscape-spec-investigate
Investigate repository files and record findings in design.md.
yujikawamodscape-spec-status
Reports spec work folder phase, file checklist, task progress, and next recommended command.
yujikawamodscape-spec-tasks
Generates a phased implementation task list from a spec-model.yaml lineage graph.
yujikawamodscape-spec-design
Designs YAML data models from spec.md and updates work-scoped spec-model.yaml iteratively.
yujikawamodscape-spec-generate
Generate table spec.md files from YAML, SQL, and Python implementation artifacts.
yujikawamodscape-spec-answer
Answers open questions in questions.md and records design impact for spec changes.
yujikawamodscape-modeling
Creates and maintains YAML-defined data models for Modern Data Stack visualization.
yujikawamodscape-spec-requirements-lite
Generates spec, design, and task documents for minor data model schema changes via the modscape CLI.
yujikawamodscape-codegen
Generate dbt, SQLMesh, or Spark SQL implementation code from Modscape YAML data models.
yujikawamodscape-spec-requirements
Gathers business requirements interactively and generates spec.md files for data pipelines.
yujikawamodscape-spec-check
Validates specification consistency and implementation readiness against a chosen SSOT artifact.
yujikawamodscape-spec-archive
Merge work-scoped YAML into the main model and archive completed data specs.
yujikawamodscape-spec-search
Search past spec archives by keyword and display relevant findings for reuse.
yujikawamodscape-spec-help
Displays the SDD workflow overview and answers questions about spec-driven development commands.
yujikawamodscape-spec-implement
Implements pending data modeling tasks from spec task lists into dbt or SQL code.
Frequently Asked Questions About yujikawa
FAQPage SchemaWhat tasks can I accomplish with yujikawa's Modscape skills?▼
You can run the full spec-driven development cycle for data models: gather requirements, investigate repositories, design models in YAML, run pre-implementation quality checks, generate task lists, implement tasks, and generate dbt, SQLMesh, or Spark SQL code, then archive completed changes.
Who are these skills designed for?▼
Analytics engineers and data engineers managing schema changes and data models. The author is a practicing analytics engineer in Japan, and the skills target teams maintaining table specs, model.yaml definitions, and transformation code across dbt, SQLMesh, or Spark SQL projects.
How do I handle a minor schema change like adding a column?▼
Use modscape-spec-requirements-lite, the lightweight SDD entry point for minor changes such as column additions, table renames, or type changes. It compresses requirements, design, and task generation into a single invocation instead of the full multi-phase flow.
What license and cost apply to these skills?▼
The OpenSpec skills (propose, explore, apply-change, archive-change) are explicitly MIT licensed and free to use. The Modscape skills do not declare a license in their frontmatter, so users should check the repository for licensing terms before redistribution.
What prerequisites are required to run these skills?▼
The four OpenSpec skills require the openspec CLI to be installed. Modscape skills operate on a project structure containing .modscape/changes folders, spec-model.yaml, model.yaml, and specs directories, so an initialized Modscape project is needed before running the SDD flow.