Ningyao
Community@v20227
Ningyao's Sakura skill suite governs the full software delivery lifecycle: specification, planning, implementation, verification, security auditing, and release preparation.
Agent Skills by Ningyao
Showing 12 vetted skills indexed across 1 GitHub repositories.
v20227sakura-security
Audit application trust boundaries and release exposure with evidence-backed security findings.
v20227sakura-research
Verify external documentation, APIs, and standards for software decisions.
v20227sakura-delegate
Delegates bounded development tasks to subagents and preserves their results in the parent context.
v20227sakura-verify
Validates software changes through executable tests, builds, and runtime evidence.
v20227sakura-release
Prepares and verifies clean user-ready release artifacts from a known source state.
v20227sakura-review
Review software changes against accepted outcomes, diffs, and verification evidence to decide pass or repair.
v20227sakura-plan
Converts accepted software outcomes into executable development plans with dependencies and checkpoints.
v20227sakura-code
Implements confirmed software features, repairs, and refactors within accepted scope and architecture.
v20227sakura-spec
Translates natural-language goals into working PRDs, feature contracts, and acceptance criteria.
v20227sakura-dev
Leads software development from requirements through decomposition, execution, verification, and delivery.
v20227sakura-simplify
Reduce code duplication, dependencies, and structural complexity while preserving accepted software behavior.
v20227sakura-fix
Diagnose reproducible software failures and apply minimal evidence-based repairs.
Frequently Asked Questions About Ningyao
FAQPage SchemaWhat tasks can I accomplish with Ningyao's Sakura skills?▼
The 12 Sakura skills cover the full delivery cycle: defining PRDs and acceptance criteria, planning multi-step changes, implementing features and refactors, diagnosing reproducible failures, running tests and builds as verification evidence, auditing security boundaries, reviewing completed work, and preparing clean releases.
Who should use the Sakura skill suite?▼
Software engineers and technical leads managing multi-step features, connected fixes, or repeated corrections benefit most. The sakura-dev skill maintains one continuous workstream across requirements, decomposition, execution, verification, and delivery, while specialist skills handle security audits, reviews, and release preparation.
How do the Sakura skills work together in practice?▼
A typical sequence runs sakura-spec to define outcomes, sakura-plan to build the smallest executable plan, sakura-code to implement, sakura-verify to confirm with tests and builds, sakura-review to judge completion, and sakura-release to publish. sakura-delegate offloads bounded subtasks to subagents.
When should I use sakura-fix versus sakura-simplify?▼
Use sakura-fix when a test, build, runtime, integration, package, or review failure has produced concrete evidence requiring diagnosis and repair. Use sakura-simplify only for requested codebase slimming or evidenced architecture congestion, reducing duplication, dependencies, and structural complexity while preserving accepted behavior.
What are the prerequisites for using these skills?▼
Each skill requires an established context: sakura-code needs a confirmed scope and clear verification method, sakura-fix needs concrete failure evidence, sakura-release needs a known source state, and sakura-security applies to requested audits or material changes to sensitive boundaries, not routine edits.