Workspace Initializer FAQs

Question 1

What files does the Workspace Init skill create?

Accepted Answer

It generates core tracking files including STATUS.md, CHECKPOINTS.md, UNITS.csv, DECISIONS.md, and GOAL.md, along with a directory structure for papers, outlines, citations, and outputs.

Question 2

When should I use the workspace-init skill?

Accepted Answer

Use this skill at the very beginning of any research pipeline or project run to establish the necessary workspace artifacts and directory skeleton required for evidence tracking.

Question 3

Why does this skill use an artifact-first approach?

Accepted Answer

An artifact-first approach ensures that research is grounded in evidence. By creating structured files like UNITS.csv and DECISIONS.md early, the skill prevents 'hollow writing' and ensures every step is documented and verifiable.

Question 4

Can I use the repository root as a workspace?

Accepted Answer

No, as a safety measure, the runner is designed to prevent initializing the repository root as a workspace. It is recommended to use a sub-directory like workspaces/my-project/.

Question 5

Will this skill overwrite my existing project files?

Accepted Answer

No, the skill is non-destructive by default. It will only overwrite existing files if the --overwrite flag is explicitly provided in the command.

Workspace Initializer

소개

주요 기능

사용 사례

Workspace Initializer

소개

주요 기능

사용 사례