meta-secret-core

Draft and update PR/MR title and description from full branch scope; use before gh pr create or gh pr edit.

Expected shape of the planning phase output before code-implementer; aligns with write-implementation-plan.

Write or update project skills and rules markdown files (.ai/skills/, .ai/rules/, .cursor/rules/). Use when creating a new SKILL.md or rule, updating an existing one, or when the user asks to document a workflow, pattern, or convention as a reusable skill.

Guard architecture, style, and security in meta-secret core crate changes.

Guard architecture, style, and security in cli/meta-cli changes.

Guard architecture, style, and security in mobile/uniffi library changes.

Guard architecture, style, and security in web-cli/ui changes.

Format a GitHub issue Summary for the feature-planner and later phases after gh issue view.

Structure a manual feature or bug report before feature-planner when not starting from a GitHub issue.

Preserve Rust workspace architecture and boundaries before coding; align with ARCHITECTURE.md.

Perform root-cause debugging before proposing fixes. Never jump directly from symptom to patch.

Optional retrospective—suggest 0–2 repo improvements (skill, command, rule, or hook) when triggers fire; otherwise say to change nothing.

Convert an approved feature direction into a concrete, architecture-safe implementation plan before coding.