Anekoique

Extract a feature SPEC from an existing codebase for brownfield Ark adoption. Produces specs/features/<slug>/SPEC.md without faking a deep-tier task. Use when the project already implements the feature and Ark needs a SPEC to reference.

Close out an Ark task by atomically committing work + task.toml + (deep tier) SPEC in one git commit. Use when the user says they're done with a task and wants to land it. Replaces the older ark-archive skill; bulk archive is now a manager-only `ark archive` CLI.

Start a standard or deep-tier Ark task. Produces PRD then PLAN, optional REVIEW on deep tier, then EXECUTE and VERIFY. Use when the user asks for feature work, refactoring, or architectural changes.

Remove an unarchived Ark task in one step. Refuses without --force when seeded files have user content. Use when the user wants to throw away a task they no longer want.

Audit every SPEC's constraints for actuator-tag health. Reports untagged rules, malformed tags, and tag/bucket mismatches across project and feature SPECs, then offers to fix them yourself or with agent assistance.

Start a research-tier Ark task. Gather a reference corpus on a topic; follow-up implementation is optional. Use when the user wants to investigate a direction before committing to a design.

Start a quick-tier Ark task. For trivial, reversible changes. Produces PRD.md only. Use when the user asks for a small fix, typo, or one-line change that's reversible in a single commit.

Record a manual session entry into the developer's workspace journal. Use when the user wants to write down notes between tasks (explorations, observations, status updates).

Use this skill when reviewing uncommitted or local code changes before commit/PR. Finds security, correctness, quality, and testing gaps, then reports only high-confidence actionable issues.

Systematically explore and present the full architecture, structure, and content of any repository. Use when onboarding to a new codebase, before major refactors, or when the user asks "how does this project work?"

Idiomatic Rust patterns, best practices, and conventions for building safe, efficient, and maintainable Rust applications.

Rust testing patterns including unit tests, integration tests, doc tests, benchmarks, property-based testing, and coverage. Follows TDD methodology with idiomatic Rust practices.

Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides comprehensive security checklist and patterns.

Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.

Start a standard or deep-tier Ark task. Produces PRD then PLAN, optional REVIEW loop on deep tier, then EXECUTE and VERIFY. Use when the user asks for feature work, refactoring, or architectural changes.

Close out an Ark task by atomically committing work + task.toml + (deep tier) SPEC in one git commit. Use when the user says they're done with a task and wants to land it. Replaces the older ark-archive skill; bulk archive is now a manager-only `ark archive` CLI.

Remove an unarchived Ark task in one step. Refuses without --force when seeded files have user content. Use when the user wants to throw away a task they no longer want.

Extract a feature SPEC from an existing codebase for brownfield Ark adoption. Produces specs/features/<slug>/SPEC.md without faking a deep-tier task. Use when the project already implements the feature and Ark needs a SPEC to reference.