chauthehienp3c1
- 11 skills
- 0 followers
- 5 days ago last updated
- ▌ Atlas Explore · chauthehienp3c1Acts as a curious, competent new joiner in the person's own role to work out what they ought to be asking about this particular system, proposes about ten questions, answers them one at a time from the registered sources with citations, raises follow-up questions and concerns (as questions to confirm, never as facts), writes what was learned back into kb/ by the normal cited route, and ends with a short recap. Remembers where the person is, so a second session resumes. Use when someone has read the orientation and does not know what to ask, asks "what should I be asking?", wants to explore or catch up on the system at their own pace, or runs /atlas-explore.
- ▌ Atlas Onboard · chauthehienp3c1 bundleWalks a new team member through catching up on the team's system, tailored to their role (developer, tech lead, solution designer or architect, BA/product, designer, QA or other), and builds that knowledge into the workspace knowledge base. Use when someone joins the team, asks to be onboarded, wants a role-specific reading path, or runs /atlas-onboard.
- ▌ Atlas Refresh · chauthehienp3c1Refreshes the team knowledge base by finding which pages are stale, re-verifying only those pages against current code and sources, updating verified_at, regenerating the index and adding a CHANGELOG entry, ready for review as a pull request. Use when check-stale or the weekly freshness report lists pages, when sources have changed, or when someone asks to refresh, update or re-verify the knowledge base.
- ▌ Atlas Reconcile · chauthehienp3c1Syncs the team's documents, work artifacts and knowledge base with what was actually built, by listing every place two layers disagree as a finding with both sides cited, asking the team to decide each one, and then updating only what a person's decision says is wrong. Use when someone asks to sync, reconcile, refresh or realign docs with the implementation, to find stale or contradictory documentation, or to go through the open findings with the team.
- ▌ Atlas · chauthehienp3c1Front door for atlas, the team knowledge-base tool. Explains what atlas is, helps create a workspace for a team or find the one you already have, and says which folder to open in Cursor. Use when someone types /atlas, asks how to get started with atlas, or wants to onboard to a team and has no atlas workspace open.
- ▌ Atlas Ask · chauthehienp3c1Answers a question about the team's system with evidence and labels, checking the knowledge base first and the sources second, then writes what was learned back into kb/ so the knowledge base grows from use. Use when someone in a team knowledge-base workspace asks how something works, why something is the way it is, who knows about something, or what the team has decided or built.
- ▌ Atlas Brief · chauthehienp3c1Generates the detail one role needs to pick up an approved story or feature (developer, QA, designer, analyst or any other role the team defines) from what exists today, cited to code or sources, plus clearly labelled agent proposals, the files expected to change, and open questions. Use when someone is about to start work on a story and asks for a brief, a task breakdown, implementation notes, test ideas or what they need to know to start.
- ▌ Atlas Check · chauthehienp3c1Compares a change (a pull request, a branch range or a set of files) with the story's acceptance criteria and the brief's declared scope, writes a check artifact with a cited verdict per criterion (met, partly met, not met or no evidence), lists files outside the scope and knowledge pages the change touches, and files a finding for each mismatch. Use when someone asks whether a change does what the story says, to review a PR against its story, to verify or test against acceptance criteria, or before saying a piece of work is done.
- ▌ Atlas Shape · chauthehienp3c1Shortens a long, repetitive or AI-generated original (a requirements document, epic, feature, user story or meeting notes) into a one-screen work artifact in which every line cites the original word for word, lists what was left out, and files a finding when the original contradicts the code or the knowledge base; or, in gate mode, reviews a draft artifact for clear scope before the team approves it. Use when someone asks to slim, trim, simplify or shape a requirement, epic, feature or story, to turn a long document into a short one, or to check that a draft artifact is ready to approve.
- ▌ Atlas Ingest · chauthehienp3c1Registers a new source (code repo, Markdown, PDF, meeting transcript, GitHub pull requests) in the team knowledge-base workspace, normalizes it through the matching adapter, updates the manifest, and judges how reliable the source is by spot-checking it. Use when someone wants to add a source, import a document or transcript, connect a repo, or has an export from Confluence, OneDrive, SharePoint or Rally.
- ▌ Atlas Verify · chauthehienp3c1 bundleHas a separate, independent agent check every statement and every diagram box and arrow of a knowledge-base page or work artifact against the exact source text it cites, removes or turns into questions whatever is not supported, and records the pass; for a slimmed work artifact it also has a second agent check that nothing material was dropped from the original. Use when a page or artifact is about to be proposed for commit (atlas-onboard, atlas-ask, atlas-refresh, atlas-shape, atlas-brief and atlas-check run it), when someone asks to verify or fact-check a page or artifact, or when a review banner says the second-agent check is missing or out of date.