Skip to content

Add README “Co dalej?” onboarding section#8

Merged
diwad-code merged 2 commits into
01_githubfrom
copilot/add-next-steps-section
May 23, 2026
Merged

Add README “Co dalej?” onboarding section#8
diwad-code merged 2 commits into
01_githubfrom
copilot/add-next-steps-section

Conversation

Copilot AI commented May 23, 2026

Copy link
Copy Markdown
Contributor

The README needed a standing “Co dalej?” section that captures current project state and next steps for someone taking over the project without prior context.

  • Onboarding state

    • Replaced the generic “Next step” section with Co dalej?.
    • Summarizes that the repo is still in Sprint 0 with no package.json, src/, or runnable game yet.
  • Continuation guidance

    • Lists the first documents to read: brief, fabula, GDD, and architecture.
    • Preserves the intended Copilot workflow and prompt order.
    • Calls out that mechanics such as combat, traits, morale, progression, factions, and quest chains should not be invented before mechanika/ is approved.
  • Maintenance rule

    • Adds an explicit instruction to keep this README section updated with current status, next steps, and blockers as the project evolves.

Copilot AI and others added 2 commits May 23, 2026 13:47
Agent-Logs-Url: https://github.com/diwad-code/SpaceshipGame/sessions/962bb575-fafe-4ae5-b548-9f66585e7c88

Co-authored-by: diwad-code <250159374+diwad-code@users.noreply.github.com>
Agent-Logs-Url: https://github.com/diwad-code/SpaceshipGame/sessions/962bb575-fafe-4ae5-b548-9f66585e7c88

Co-authored-by: diwad-code <250159374+diwad-code@users.noreply.github.com>
@diwad-code diwad-code marked this pull request as ready for review May 23, 2026 13:48
Copilot AI review requested due to automatic review settings May 23, 2026 13:48

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds a standing “Co dalej?” (What next?) onboarding section to the README to capture current project status and actionable next steps for a new maintainer in Sprint 0.

Changes:

  • Replaces the previous “Next step” section with a new “Co dalej?” section describing Sprint 0 status and an ordered onboarding flow.
  • Lists the first docs to read and reiterates the intended Copilot slash-command workflow/order.
  • Adds an explicit maintenance instruction to keep this section updated with current status, next steps, and blockers.

Comment thread README.md
Comment on lines +40 to +61
## Co dalej?

Ta część ma być aktualizowana na bieżąco, tak aby kolejna osoba mogła przejąć projekt bez wcześniejszego kontekstu.

Aktualnie projekt jest w Sprint 0: porządkowana jest dokumentacja, workflow Copilota i materiały wejściowe. Nie ma jeszcze `package.json`, katalogu `src/` ani uruchamialnej wersji gry.

Najbliższe kroki:

1. Otwórz repozytorium w VS Code z włączonym GitHub Copilot Chat.
2. Przeczytaj najpierw:
- `docs/GAME_BRIEF.md` — czym ma być gra,
- `docs/FABULA.md` — aktualny kanon fabularny,
- `docs/GDD.md` — uporządkowany projekt gry,
- `docs/ARCHITECTURE.md` — zasady techniczne i miejsca przyszłej integracji.
3. Używaj komend Copilota zgodnych z polem `name:` w plikach `.github/prompts/`:
- `/game-dev` — sprawdzenie stanu repo i wybór kolejnych 1-3 kroków,
- `/game-brief` — dopracowanie trwałego opisu projektu,
- `/fabula` — rozwijanie biblii fabularnej przed zamknięciem mechanik,
- `/gdd` — utrzymanie dokumentu projektowego w zgodzie z briefem i fabułą,
- `/skills-adoption` — wdrażanie zatwierdzonych skillów i MCP z dokumentacji,
- `/investigate`, `/new-scene`, `/new-system`, `/new-event`, `/data-schema`, `/pwa-check`, `/mobile-ux`, `/code-review`.
4. W Sprint 0 trzymaj kolejność pracy: `/game-dev` → `/game-brief` → `/fabula` → `/gdd` → `/skills-adoption`.
@diwad-code diwad-code merged commit b8a22d1 into 01_github May 23, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants