Bootstrap

This skill configures the repository-local .skills/ files used by sirius-skills.

When requested, it also scaffolds a lightweight docs/wiki/ layer with features/, concepts/, index.md, and log.md.

It supports three modes:

• default: write the supported config files with generic defaults
• jira: write the supported config files plus Jira-oriented conventions
• ask: ask the user which mode to use before writing any config

Mode selection

Choose the mode from the user request:

• If the user explicitly asks for a generic setup, use default.
• If the user explicitly asks for Jira support or ticket-based conventions, use jira.
• If the user says "configure the project" or is otherwise ambiguous, use ask and stop to ask which mode they want.

Do not silently assume Jira. The only time this skill should ask the user to choose a mode is the explicit ask path.

Workflow

1. Inspect the current repository config

Read these files when they exist:

• .skills/planning.json
• .skills/execution.json
• .skills/conventions.json

Preserve unrelated keys in existing JSON files. This skill should only update the supported configuration surface it owns.

2. Resolve the config values

Use these defaults unless the user asked for different values:

• planning_dir: docs/features
• proposal_dir: docs/proposals
• design_diagram_mode: embedded
• slice_dir: slices
• preferred_workflow: TDD
• auto_start_implementation: true

For jira mode, use these preset conventions unless the user supplies project-specific values:

• issue_sliceer: jira
• id_pattern: ^[A-Z][A-Z0-9]*-[0-9]+$
• branch_extract_pattern: ^([A-Z][A-Z0-9]*-[0-9]+)-(.+)$
• commit_format: {ID}: {summary}
• pr_title_format: {ID}: {summary}
• issue_url_template: https://jira.example.com/browse/{ID}

If the user already gave a real Jira URL, use it instead of the placeholder.

If the user also wants a wiki scaffold, use these defaults:

• wiki root: docs/wiki
• feature synthesis pages: docs/wiki/features
• cross-cutting concept pages: docs/wiki/concepts
• wiki index: docs/wiki/index.md
• append-only log: docs/wiki/log.md

Do not assume the wiki should be created unless the user asked for it.

3. Run the helper script

Use the bundled helper to create or update the files deterministically:

python3 skills/bootstrap/scripts/bootstrap.py --mode default

Add --wiki when the user also wants the wiki scaffold:

python3 skills/bootstrap/scripts/bootstrap.py --mode default --wiki

Jira mode:

python3 skills/bootstrap/scripts/bootstrap.py \
  --mode jira \
  --issue-url-template "https://jira.example.com/browse/{ID}"

If the user wants custom planning or execution layout, pass those values too:

python3 skills/bootstrap/scripts/bootstrap.py \
  --mode default \
  --wiki \
  --planning-dir planning/features \
  --proposal-dir planning/proposals \
  --design-diagram-mode linked_svg \
  --slice-dir specs \
  --workflow TDD \
  --auto-start-implementation

4. Validate the generated files

After running the helper:

• read back the written JSON files
• confirm the mode-specific values are present
• when --wiki was used, confirm docs/wiki/index.md, docs/wiki/log.md, docs/wiki/features/, and docs/wiki/concepts/ exist
• summarize the result for the user

If the helper reports invalid existing JSON, surface that error instead of overwriting the file blindly.

Ask mode

When the request does not choose default or jira, ask the user which mode to apply before running the helper.

Recommended choices:

• default
• jira

Once the user chooses, continue with the matching workflow above.

Output expectations

Successful runs should leave the repository with:

• .skills/planning.json
• .skills/execution.json
• .skills/conventions.json

When --wiki is used, successful runs should also leave the repository with:

• docs/wiki/index.md
• docs/wiki/log.md
• docs/wiki/features/
• docs/wiki/concepts/

The generated wiki scaffold is intentionally generic. Repositories can refine their wiki rules and page placement in AGENTS.md later without changing the bootstrap defaults.

When .skills/planning.json includes design_diagram_mode: "linked_svg", planning/design skills should place diagram source and generated SVGs under <feature_path>/figures/, link the SVGs from system-design.md, and keep the figures on an explicit white background using skinparam backgroundColor white plus a white SVG canvas rect.

In default mode, .skills/conventions.json may remain an empty object so the repo keeps its generic behavior explicit without inventing project-specific workflow rules.

Examples

Example 1: Generic setup

Request: "Configure this repo for sirius-skills with the default setup."

Action:

1. Use default mode.
2. Apply the default planning and execution directories.
3. Create .skills/conventions.json as {} when it does not already exist.

Example 2: Default setup with wiki

Request: "Configure this repo for sirius-skills and scaffold the wiki."

Action:

1. Use default mode.
2. Run the helper with --wiki.
3. Confirm the wiki scaffold uses docs/wiki/features/ and docs/wiki/concepts/.

Example 3: Jira setup

Request: "Set this project up with Jira conventions."

Action:

1. Use jira mode.
2. Apply the Jira preset fields in .skills/conventions.json.
3. Use the real Jira browse URL if the user provided one.

Example 4: Ambiguous request

Request: "Configure the project."

Action:

1. Use ask mode.
2. Ask the user whether they want default or jira.
3. Only write config after they choose.