Review an implementation for accuracy, completeness, and quality against a Portweave spec at .ai/specs/<slug>/<slug>.md. Use when reviewing code, verifying a spec was implemented correctly, or auditing changes against the spec. Invoked as a required gate by the `execute-spec` skill alongside the global `/security-review` skill, both running in parallel as subagents before a spec can be marked `shipped`.
Draft a per-feature what/why document at .ai/features/<slug>/<slug>.md. Use when the user wants to define a new feature's motivation and scope before writing a spec. Stops at the feature doc — implementation specs and code are separate skills (create-spec, execute-spec).
Draft an implementation spec for a Portweave feature at .ai/specs/<slug>/<slug>.md. Use when the user wants to plan the implementation of a feature whose what/why is already captured in a feature doc (or alongside drafting one). Follows Portweave's spec template (Problem / Approach / Acceptance criteria / Open questions).
Implement an approved spec from .ai/specs/<slug>/<slug>.md. Use when the user references a spec ("execute the X spec", "let's build what's in spec Y", "implement .ai/specs/foo/foo.md"). Reads the spec, plans the changes, writes tests, implements code, runs dev-workflow, then runs parallel code-review + security-review subagents as a required gate before shipping.