anujgupta19/RunningWrapped / .claude/skills/milestone
milestone
VerifiedWork on the next (or a named) step from docs/ROADMAP.md in learning mode β plan, explain concepts, implement a small slice, verify, then update the roadmap and learning log. Use when the user says "next step", "continue", "let's do 1.4", or similar.
/milestone: one roadmap step, learning mode
1. Orient
- Read
docs/ROADMAP.md. If an id was given, use that step. Otherwise use the first unchecked step. - Read the relevant CLAUDE.md (
backend/ormobile/) and any docs the step touches (DATA_MODEL.md,ARCHITECTURE.md). - Look at the current code so the plan fits what exists.
2. Brief (then wait)
Post a short brief and wait for the go-ahead before writing code:
- Goal: what will exist and work at the end of this step.
- Concepts you'll meet: 2β5 Java/Spring (or RN) concepts, each one line, with a Go/TS analogy where it helps.
- Plan: the files to create or change, in order.
- Your turn? If the step has a π§βπ» marker or a self-contained piece, offer to let the user write it, giving a precise spec
(signature, behavior, a hint) and saying you'll review it with
/java-review.
If invoked with --you-drive, the user writes all of the code: give them the spec and hints, then review.
3. Build in small increments
- Make the change in 1β3 small chunks. After each chunk, explain the non-obvious lines, especially annotations
("what does
@Transactionalactually do here?"). - Follow
backend/CLAUDE.md/mobile/CLAUDE.mdstrictly. Don't add anything the step doesn't need. - If a decision in the docs turns out wrong, stop and propose the change rather than silently deviating.
4. Verify
- Backend:
./mvnw test(orverifywhen there are integration tests). Run the app andcurlthe endpoint when relevant. - Mobile:
npm run typecheck && npm run lint && npm test. Tell the user what to look at in the simulator. - Report failures honestly, with output.
5. Wrap up
- Tick the step in
docs/ROADMAP.md. - Append an entry to
docs/learning/LEARNING_LOG.md(concepts, where to look, one gotcha, one link). - Suggest a commit message. Do not commit or push: the developer does that themselves.
- Give a one-line preview of the next step, then stop.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 467k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product β it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product β not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial β a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK β model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER β read BEFORE opening the target file; don't skip because it "looks like a one-liner" β whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) β never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named β don't Read the file). | Stars: 196k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |