cj-stack

Plugin cj-stack from marketplace cj-stack in cpeaustriajc/cj-stack. Commands read from the repo's manifest — 18 days ago.

Skills (13)

• hone

  This skill should be used when the user says "hone", "hone" followed by a skill name, "what do I keep correcting", "reflect", "learn from my sessions" or "why does Claude keep doing X", or after a session with several corrections. It mines past Claude Code transcripts for recurring corrections and f

• project-knowledge

  This skill should be used when the user says "note that down as a decision", "what did we decide about X", "supersede that decision", asks to record research or a finding, or a decision is made in conversation that others will need. It keeps a decision log and research pages for people in the team's

• grill

  This skill should be used when the user says "grill me", "ask me questions first", "stress-test this", "poke holes in this" or "plan and ask me" about a change, design, feature or plan. It sizes the work, then interviews in short rounds of questions with a recommended answer each until no decision i

• shape

  This skill should be used when a project, epic, spec or milestone is created, restructured or audited in any tracker; when the user says "shape this", "put this in a doc", "write the spec" or "set a milestone"; when a spec arrives pasted into one ticket; when direction changes after a demo; and for

• tickets

  This skill should be used when the user says "ticket", "break this into tickets", "cut the next slice", "write the issue", "file these bugs as issues", "review ABC-123" or "rewrite this ticket", after shape confirms a spec, and when a ticket is too long or does two things. It cuts thin, demoable sli

• vision

  This skill should be used when the user brings a product idea or vision, asks "is this worth building", says "grill me on this idea", "plan the product", "set up the initiative" or "what are the features", wants a plan from product down to tickets, wonders whether a personal tool could sell, or asks

• break-it

  This skill should be used when the user says "break it", "try to break this", "dumb user", "monkey test", "bug bash", "dogfood" or "QA this like a user", and after a change to a user flow (forms, checkout, multi-step flows) before review. It drives the running app or a design prototype as a careless

• feature-files

  This skill should be used when writing or updating a feature file, when an E2E check needs to know how to reach and drive an area of the app, when verifying a change in the running app, when break-it needs a starting point, and when a UI change makes a feature file wrong. It keeps one short file per

• interrogate

  This skill should be used when the user says "interrogate", "second opinion" or "cross-check this", or before opening a PR on a risky change (auth, money, data migrations, concurrency). It reviews a diff with fresh reviewers that each see a different slice of it, then verifies, filters and ranks the

• playbooks

  This skill should be used when fixing a bug, refactoring, chasing a performance problem, building a feature from a ticket, prototyping a design, or designing an API, module or data shape before building it, at the start of any such task bigger than a one-line change. It routes the work to its playbo

• ui-polish

  This skill should be used when the user asks to review a UI against its design, polish spacing, type, colour or motion, or sign off a visual change, and before asking for visual sign-off. It compares the screen with the design and a list of common mistakes, and reports a Before/After/Why table with

• commit

  This skill should be used when the user asks to commit their work: "commit", "commit and push", "make commits in the repo's style" or "split these changes into commits". It commits the uncommitted changes in small logical slices with messages in the repo's style, then pushes the current branch ("loc

• create-pr

  This skill should be used when the user asks to open a pull request: "open a PR", "make a PR for this branch", "create a draft PR" or "PR this against develop". It commits, runs the fast checks, pushes and opens a PR that links the issue and the evidence ("draft" for a draft, or a base branch). The

Similar plugins