Ctrl K

Quick Ref / Command

Engineer Kit

/ak:project-organization

File layout and naming

Single source of truth for file placement, kebab-case naming, plan/report/doc templates, and safe organize-mode migrations.

Classify artifact

Choose base path

Name by temporality

Resolve nesting

Rule 01

Every file has a category before it has a path

Rule 02

Kebab-case, self-documenting slugs are the default for non-language-specific files

Rule 03

Plans and agent outputs live under plans/, not ad hoc roots

Rule 04

Organize mode is proposal-first and confirmation-gated

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

Start

Input, scope, route

1 Classify artifact Decide whether the item is source, test, plan, research, report, doc, asset, script, or config.
2 Choose base path Apply the directory categories: docs/, plans/, tests/, scripts/, assets/{type}/, guides/, root, or .config/.

Work

Agent / skill execution

3 Name by temporality Use timestamped names for plans/reports/journals, evergreen slugs for stable docs, and variant suffixes for asset versions.
4 Resolve nesting Keep single outputs flat; create self-contained folders for multi-file work, parent-scoped reports, platform folders, or variant sets.

Verify

Gate, review, validation

5 Apply markdown shape For markdown, start with H1, add frontmatter only when tooling consumes it, and use the required section order for the document type.
6 Propose migration When organizing existing files, scan targets, list from→to moves, surface conflicts, then wait for confirmation.

Report, handoff, artifact

7 Execute and verify Create needed directories, move approved files without overwriting, then show the final structure and remaining issues.

Syntax, arguments, subcommands

How to invoke the skill: syntax, positional arguments, shared options, then each subcommand with its own syntax and outcome.

Syntax

/ak:project-organization [directories or files to organize]

Arguments

[directories or files to organize]

Targets

Optional directories or files to organize. Direct targets trigger scan → analyze → propose → confirm → execute → verify; omitted or cross-skill use returns path and naming guidance.

/ak:project-organization docs/ plans/

Modes / Routes

Advisory

Return path guidance

Research:: Uses requested artifact type and naming rules
Review:: None
Validate:: No file moves

Organize

Scan and migrate after approval

Research:: Categorizes target dirs/files
Review:: None
Validate:: Conflict check before moving

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Path decision Recommended

/ak:project-organization plans and reports for the auth refactor

Use when:: Use when another skill needs the canonical location before writing.
Expected:: Returns the correct category, path pattern, naming mode, and placement rationale before any file is written.

Organize folder

/ak:project-organization docs/ plans/

Use when:: Use when existing files need a proposed migration table.
Expected:: A scan, violations, from-to plan, approval gate, and final verification after approval.

Handled Scope

Directory taxonomy
Timestamped plan/report naming
Markdown body templates
Safe file migration
Cross-skill output paths

Artifacts Produced

Canonical paths

Pattern

plans/{date-slug}/, plans/reports/, docs/, assets/{type}/, scripts/

The deliverable is either path advice or a confirmed migration table with final structure.