xiongxianfei

architecture

Create or update technical architecture after Proposal Review and before the specification is finalized.

AI & Automation Solid

ci-maintenance

Author or review repository-owned CI workflows, validation automation, and related configuration when coverage, speed, caching, permissions, triggers, or ordinary hardening needs maintenance.

Review an implementation slice against the actual diff, approved design and delivery packages, tests, and validation evidence, then record findings or a clean first-pass review. Use after implement hands off a milestone or when implementation review is requested. Use design-review, delivery-review, verify, or pr for those gates instead.

implement

Implement one approved milestone or isolated implementation request with tests or proof first, then hand it to code-review with validation evidence. Use when requirements, scope, and validation commands are clear enough to code. Use bugfix for defect reproduction/fix loops, code-review to review implementation, verify for final readiness, and pr for PR handoff.

plan-review

Review an execution plan for alignment, sequencing, scope, dependencies, validation, recovery, risk, and implementation readiness. Use other skills for authoring, implementation, verification, and PRs.

plan

Create or revise a stable execution plan after proposal, spec, and architecture are settled enough to implement. Use for multi-file, multi-component, risky, migration-heavy, or milestone-based work that needs reviewable implementation slices, verification allocation, validation commands, recovery paths, and dependencies. Do not use plan to choose product direction, write code, review diffs, update workflow routing or existing planned work, verify branch readiness, or open PRs.

project-map

Build, refresh, or audit a current-state repository orientation map with cited evidence, bounded inference, known gaps, and durable root or area scope.

proposal-review

Review a concise proposal and its embedded feasibility evaluation before Design. Use when the user asks whether a direction is valuable, bounded, feasible, vision-aligned, and specific enough to pursue without prematurely settling downstream decisions. Use proposal to write proposals; use design-review, delivery-review, code-review, verify, or pr for later gates.

proposal

Create a concise direction-approval proposal before Design. Use when the user has a selected direction, explored options, problem statement, or issue that needs its challenge, goals, bounds, governing principle, direction, and feasibility recorded. Use proposal-review to review an existing proposal; use architecture and spec for detailed Design decisions.

spec-review

Review a feature spec before architecture, test planning, planning, or implementation. Use when the user asks to challenge requirement clarity, normative language, completeness, testability, examples, compatibility, observability, security/privacy, non-goals, acceptance criteria, or readiness. Use spec to write specs; use proposal-review, architecture-review, plan-review, code-review, verify, or pr for those stages.

Testing & QA Solid

test-spec-review

Independently review an active test specification before implementation. Use to assess proof-map alignment, requirement and edge-case coverage, milestone mapping, validation commands, fixtures, automation versus manual evidence, and implementation handoff readiness. Use test-spec to author or revise the proof map; use code-review and verify for implemented tests and final evidence.

Testing & QA Solid

test-spec

Generate a traceable test specification from an approved feature spec and execution plan before writing test code or production code. Use to map requirements, examples, edge cases, architecture boundaries, and milestones into concrete tests.

vision

Produce or update the project vision and matching README front-matter at project genesis or when current vision no longer reflects the project. This skill is upstream of the per-change workflow.

explore

Expand a materially unclear problem or solution space into distinct directions before its decision owner commits. Use when framing, user value, scope, reversibility, or available options are unsettled; use research instead when the options are known and an uncertain fact is the blocker.

research

Reduce a bounded, decision-relevant factual uncertainty with attributable evidence and explicit confidence. Use when platform behavior, compatibility, standards, policies, prices, performance, security, scale, or operational facts could materially change a known decision; use explore instead when the option space itself is unclear.

delivery-review

Independently review one plan-centered delivery package before implementation. Judge safe sequencing and verification adequacy together; use plan for delivery and verification allocation and spec for behavioral gaps.

design-review

Independently review architecture, specification, applicable ADRs, and accepted proposal constraints as one design package before delivery planning. Use design-review for design coherence and package authority; use architecture and spec for authorship.

architecture-review

Review a proposed architecture/design before execution planning. Use for cross-component, hard-to-reverse, data, security, performance, migration, or long-lived design decisions.

bugfix

Diagnose or fix unexpected behavior, failing evidence, incidents, regressions, and bug reports with bounded authority and identity-stable proof.

constitution

Create or update the repository's governing AI-development principles. Use when starting a project, adopting this skill pack, onboarding a brownfield codebase, or when recurring mistakes show that project rules are unclear.

explain-change

Trace meaningful changes from the actual diff to decisions, requirements, tests, reviews, and validation. Use after implementation or for a change-rationale question.

learn

Capture durable lessons after implementation, review, verification, or incidents. Use when recurring mistakes, systemic gaps, or explicit retrospective work should guide future contributors.

pr

Prepare a verified pull request from actual diff and evidence.

verify

Run final verification and produce durable change rationale only on success, with optional PR handoff. Use to verify artifact-code-test coherence, requirement coverage, validation commands, CI readiness, drift, release safety, and scoped direct validation checks.

workflow

Orchestrate the full spec-driven, test-driven agentic development lifecycle. Use when starting, resuming, auditing, or routing work through the standard RigorLoop workflow. This skill assesses workflow state, enforces artifact order, and keeps exploration, specification, architecture, planning, tests, implementation, review, rationale, verification, PR, and learning connected.

route

Route, resume, audit, and orchestrate bounded RigorLoop workflow execution using authoritative CLI context. Use when starting or continuing governed work, interpreting blockers or findings, selecting correction ownership, or managing bounded workflow automation.