bonnguyenitc

bonnguyenitc/specship

Command Claude Code

Run tests, commit current work, push, and open a PR.

bonnguyenitc/specship

Command Claude Code

Release specship to npm via publish.sh (dry-run first).

bonnguyenitc/specship

Command Claude Code

Install specship into a scratch dir and verify the result end-to-end.

bonnguyenitc/specship

Settings file Claude Code

Agent settings declaring 9 allowed tools.

bonnguyenitc/specship

Cursor rule Cursor

Staged spec→plan→coding→review workflow with shared task state on disk.

bonnguyenitc/specship

Instructions file GitHub Copilot

Instructions for bonnguyenitc/specship: For any non-trivial change, follow .specship/skills/WORKFLOW.md and the per-stage playbooks in .specship/skills/ss- /SKILL.md.

bonnguyenitc/specship

Instructions file

Instructions for bonnguyenitc/specship, covering specship — dev guide, verify every change and learnings.

bonnguyenitc/specship

Agent

Read-only search worker for the specship pipeline. Use to delegate one wide fan-out sweep when a stage needs an answer that means reading many files — it returns verified conclusions only, so the caller's context stays clean. A stage invokes it, never a user directly; it never writes or changes code.

bonnguyenitc/specship

Agent

External-fact search worker for the specship research stage. Use to run one query angle of a larger question and return verified, cited conclusions. One invocation per angle — it gathers and checks its own sources, and it neither picks the angles nor writes the report.

bonnguyenitc/specship

Agent

Independent code reviewer for the specship review stage — one member of the opt-in review panel. Use to get fresh, context-free eyes on a working diff, optionally through a named lens (correctness, security, performance, contract-consistency). Reports findings only; it does not fix code, decide the verdict, or touch…

bonnguyenitc/specship

Skill Claude CodeCodex

Retire a finished or abandoned task by relocating its whole folder into tasks/archive/, history preserved, so scans over the active set skip it. Use for a task that is finished or has been abandoned, or when asked to "archive", "shelve", "put this task away", "lưu trữ task", "dọn task xong". Reversible via…

bonnguyenitc/specship

Skill Claude CodeCodex

Implement an approved plan step by step, following the project's conventions, and verify each step. Use after a plan exists, when asked to "implement this", "code it up", "build the feature", or "code đi". Writes minimal, surgical code matching existing style and runs each success check before starting the next step.…

bonnguyenitc/specship

Skill Claude CodeCodex

Diagnose and fix a bug methodically, and track the investigation in the owning task. Use when something is broken, a test fails, behavior is wrong, or asked to "debug X", "fix this bug", "why is this failing". Reproduces, finds root cause, fixes minimally, verifies, and records it in tasks/TASK- /debug.md. Attaches to…

bonnguyenitc/specship

Skill Claude CodeCodex

Explore and explain an unfamiliar codebase for onboarding. Use when a developer joins a project, when asked to "understand the codebase", "explain the architecture", "how does this project work", "where is X handled", or before making changes in code you haven't seen yet. Produces a structured map of stack…

bonnguyenitc/specship

Skill Claude CodeCodex

Deliberately set an in-progress task aside to pick up later — mark it paused with a reason, leaving every pipeline artifact untouched. Use when work halts by choice rather than by a blocker, or when asked to "pause", "park", "hold this task", "tạm dừng task", "để task này lại sau". The inverse of ss-resume-task…

bonnguyenitc/specship

Skill Claude CodeCodex

Design an implementation plan from a confirmed spec before writing code. Use after the spec is confirmed, when asked to "plan this feature", "how should we implement X", "break this down into steps", or "lên kế hoạch". Produces an ordered, verifiable step-by-step plan with files to touch, approach, tradeoffs, and…

bonnguyenitc/specship

Skill Claude CodeCodex

Research a topic, technology, library, or decision using the strongest search tool available in the session. Use when asked to "research X", "compare X vs Y", "find the best library/tool for X", "what's the latest on X", "how does work", or whenever an answer depends on external facts (versions, APIs, pricing…

bonnguyenitc/specship

Skill Claude CodeCodex

Pick up an in-progress task exactly where it was left off — locate it, report where it stands, and continue from the current stage. Use when returning after a break or context reset, or when asked to "resume", "continue the task", "pick up where we left off", "tiếp tục task", "đang làm tới đâu rồi". Entry point over…

bonnguyenitc/specship

Skill Claude CodeCodex

Wrap up a finished change — self-review the diff, run the full test/lint gate, verify against acceptance criteria, update docs, then prepare commit/PR. Use after coding is done, when asked to "review my changes", "wrap up", "finalize", or "is this ready to merge". Final stage of the specship pipeline.

bonnguyenitc/specship

Skill Claude CodeCodex

Take a feature request from idea to reviewed, ready-to-commit code in one run — spec → plan → coding → review (+ debug on defects) — without asking at each stage. Use when given a request like "/ss-ship implement login", "ship this feature", "do the whole flow for X", "làm hết flow cho chức năng X". Orchestrator over…

bonnguyenitc/specship

Skill Claude CodeCodex

Read and fully understand a spec, ticket, PRD, or feature request before any planning or coding. Use when given requirements to implement, when asked to "understand this spec", "what does this ticket mean", or as the first step of a feature. Extracts goals, requirements, acceptance criteria, edge cases, and open…