ArcQian-bit
- 8 skills
- 0 followers
- 15 hours ago last updated
- ▌ To Prd · arcqian-bit bundleTurn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.
- ▌ Triage · arcqian-bit bundleTriage issues through a state machine driven by triage roles. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.
- ▌ Caveman · arcqian-bit bundleUltra-compressed communication mode. Cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes caveman.
- ▌ Handoff · arcqian-bit bundleCompact the current conversation into a handoff document for another agent to pick up. Use when the user wants to hand work to a fresh session, preserve context before compaction, or create a continuation brief.
- ▌ Zoom Out · arcqian-bit bundleTell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.
- ▌ To Issues · arcqian-bit bundleBreak a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
- ▌ Setup Real Engineer Skills · arcqian-bit bundleSets up Codex project instructions in AGENTS.md plus docs/agents/ so the real-engineer skills know the repo's issue tracker, triage label vocabulary, and domain doc layout. Use before first use of to-issues, to-prd, triage, diagnose, tdd, improve-codebase-architecture, or zoom-out, or when those skills lack project context.
- ▌ Improve Codebase Architecture · arcqian-bit bundleFind deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.