agentleFS
Sign inStart free
timjrobinsontimjrobinson/Claude-Code-Construction-Manager/.claude/skills/start/SKILL.md

start

Skill4 starsChanged 8 months agoMITView on GitHub

First-time onboarding — asks where you are, then guides you to the right workflow. No assumptions.

130 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use setup-engine, team-audio and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • CoralGameSkill

    setup-engine

    Configure the project's game engine and version. Pins the engine in CLAUDE.md, detects knowledge gaps, and populates engine reference docs via WebSearch when the version is beyond the LLM's training data.

    Also in 13 projects that use this

  • CoralGameSkill

    team-audio

    Orchestrate audio team: audio-director + sound-designer + technical-artist + gameplay-programmer for full audio pipeline from direction to implementation.

    Also in 13 projects that use this

  • lilangMaxSkill

    create-stories

    Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.

    Also in 11 projects that use this

  • lilangMaxSkill

    story-done

    End-of-story completion review. Reads the story file, verifies each acceptance criterion against the implementation, checks for GDD/ADR deviations, prompts code review, updates story status to Complete, and surfaces the next ready story from the sprint.

    Also in 11 projects that use this

  • +4 more from CoralGame
  • +3 more from lilangMax

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 117 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before asking anything, silently gather context:

    line 15
  2. Very specific:

    Project configured?: Read .claude/docs/technical-preferences.md.

    line 17
  3. Very specific:

    Project brief exists?: Check for design/architectural/project-brief.md.

    line 18
  4. Very specific:

    Specifications exist?: Check for files in specs/.

    line 20
  5. Very specific:

    Production artifacts?: Check for files in production/phases/ or production/milestones/.

    line 21

“Common” is measured: kept by at least 6 in 10 of the 117 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Guided Onboarding

Workflow

1. Detect Project State (Silent)

Before asking anything, silently gather context:

  • Project configured? Read .claude/docs/technical-preferences.md. If Building Type is [TO BE CONFIGURED], not set.
  • Project brief exists? Check for design/architectural/project-brief.md.
  • Design docs exist? Count markdown files in design/.
  • Specifications exist? Check for files in specs/.
  • Production artifacts? Check for files in production/phases/ or production/milestones/.

2. Ask Where the User Is

Welcome to Claude Code Construction Team!

Before I suggest anything, I'd like to understand where you're starting from.

A) No idea yet — I don't have a building concept. I want to explore options.

B) Vague idea — I have a rough building type or site in mind but nothing concrete.

C) Clear requirements — I know the building type, site, and basic program but haven't formalized documents.

D) Existing project — I already have design docs, drawings, or significant planning done.

Wait for response.

3. Route Based on Answer

If A: No idea → /brainstorm

If B: Vague idea → /brainstorm [hint]

If C: Clear requirements → /setup-project-type then /map-systems

If D: Existing project → /project-stage-detect

4. Confirm Before Proceeding

Present recommended path and ask which step to take first. Never auto-run.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free