setup

Generate a WORKSPACE.md file defining artifact roots and tracker integration settings.

1|Updated Jul 1, 2026
One-click install
npx skills add https://github.com/marcuskrogh/skills --skill setup-marcuskrogh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup
Source: https://github.com/marcuskrogh/skills/tree/main/skills/setup
Command: npx skills add https://github.com/marcuskrogh/skills --skill setup-marcuskrogh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill resolves configuration drift and ambiguity in agent-driven repositories by establishing a single source of truth for issue tracking, artifact paths, and delivery conventions.

Core Features & Use Cases

  • Workspace Alignment: Standardizes the environment by generating a WORKSPACE.md file that guides all subsequent pipeline skills.
  • Multi-Tracker Support: Integrates with markdown-based local tracking, Jira, GitHub Issues, or Linear.
  • Use Case: When onboarding a new repository, use this skill to define where your roadmap, plans, and bug reports live, ensuring the agent knows exactly how to interact with your project management tools.

Quick Start

Run the setup skill to configure the issue tracker and workspace paths for this repository.

Frequently Asked Questions about setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize workspace configuration for agent-assisted development repositories?

Standardize workspace configuration by generating a canonical WORKSPACE.md file that defines artifact roots, delivery branches, and tracker integration settings. This establishes a single source of truth for issue tracking and pipeline conventions to prevent configuration drift across agent-driven repositories.

What's the best way to align a development workspace with Jira, GitHub Issues, or Linear?

Align a development workspace by running a setup process that configures multi-tracker support for Jira, GitHub Issues, Linear, or local markdown tracking. It generates a WORKSPACE.md file ensuring the agent knows exactly how to interact with project management tools and where roadmaps live.

Why does configuration drift happen in agent-driven repositories?

Configuration drift happens in agent-driven repositories due to ambiguity in issue tracking, artifact paths, and delivery conventions. Resolving it requires establishing a single source of truth through a canonical WORKSPACE.md artifact that guides all subsequent pipeline skills.

Can I use markdown-based local tracking for my project onboarding instead of external issue trackers?

Yes, you can use markdown-based local tracking for project onboarding instead of external trackers. The setup process supports markdown integration, alongside Jira, GitHub Issues, and Linear, allowing the agent to interact seamlessly with your chosen project management tool.

How do I onboard a new repository to ensure the agent knows where my bug reports and plans live?

Onboard a new repository by running the setup skill to configure the issue tracker and workspace paths. This creates a WORKSPACE.md artifact defining where roadmaps, plans, and bug reports live, ensuring the agent knows exactly how to interact with your project management tools.

Does workspace alignment require a specific artifact to define delivery branches and tracker integration?

Yes, workspace alignment requires the creation of a canonical WORKSPACE.md artifact. This file defines artifact roots, delivery branches, and tracker integration settings, serving as the single source of truth that guides all subsequent pipeline skills and environment synchronization.