alicankiraz1

Use when defining plans, specs, or task breakdowns for web application work that may be missing security requirements

Use when a repository wants stage-aware cybersecurity guidance during planning, risky implementation changes across authentication, authorization, tokens, secrets, middleware, outbound requests, file handling, CI, deployment, and other trust boundaries,…

Use when implementation is complete or review is requested and the user may want a focused security review of the changed code

Use when a feature or project is nearing handoff or release and the user may want a stack-aware security check plan without automatic setup

Use when a session needs quick orientation to SentinelXPrime stages, checkpoints, guardrails, and the right SentinelXPrime skill to invoke

Use for CursorQB Step 3 when existing Step 2 sub-plans need coverage, consistency, readiness, ontology, ledger, and security audit.

Use for CursorQB Step 1.5 when an existing project needs a read-only autopsy and optional Project-Ontology.md before Step 2.

Use for gated CursorQB Step 4 implementation when an audited plan has READY or READY_WITH_WARNINGS slices and the user approved code changes.

Use when the user runs /cursorqb-plan or asks CursorQB to plan a project end to end with repo-aware intake, autopsy, ontology, ledger memory, audit, and gated implementation.

Use for CursorQB Step 2 when Main-Planing.md must be decomposed into phase folders, sub-plans, Sub-Planing-Index.md, and a v3 planning ledger.

Use when a repository wants stage-aware cybersecurity guidance during planning, risky implementation changes across authentication, authorization, tokens, secrets, middleware, outbound requests, file handling, CI, deployment, and other trust boundaries,…

Use when defining plans, specs, or task breakdowns for web application work that may be missing security requirements

Use when implementation is complete or review is requested and the user may want a focused security review of the changed code

Use when a feature or project is nearing handoff or release and the user may want a stack-aware security check plan without automatic setup

Use when planning repo work with evidence-backed comprehension, autopsy, ontology, ledger continuity, QA audit, and gated handoff.

Crawl web documentation into context for accurate, up-to-date coding assistance. Supports quick single-page lookups and deep multi-page indexing with search.

Vibecoding-first Antigravity planning with evidence-backed comprehension, autopsy, ontology, ledger continuity, helper-agent-aware QA, and gated handoff.

Claude Code planning with evidence-backed comprehension, autopsy, ontology, ledger continuity, QA audit, and gated handoff.

Vibecoding-first project planning workflow for Kimi Code. Use to create Planner-docs/Main-Planing.md, run an existing-project autopsy, maintain comprehension, ontology, and ledger context, decompose phases into sub-plans, audit readiness, and print gated…