finishing-task

Validate completed task outcomes and promote learnings to project memory.

7|2|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/yishan-io/yishan-mono --skill finishing-task
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finishing-task
Source: https://github.com/yishan-io/yishan-mono/tree/main/packages/pi-task/skills/finishing-task
Command: npx skills add https://github.com/yishan-io/yishan-mono --skill finishing-task

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of incomplete task records and lost project knowledge by enforcing a structured, durable wrap-up process for tracked tasks.

Core Features & Use Cases

  • Durable Completion: Ensures tasks are finished with a factual, verified outcome rather than just being abandoned.
  • Knowledge Promotion: Automatically identifies and promotes project-wide learnings, decisions, and architecture facts into persistent memory.
  • Use Case: When a developer finishes a feature implementation, they use this skill to verify the work, document the final outcome, and ensure that any new architectural decisions are captured in the project's long-term memory.

Quick Start

Instruct the agent to finish the current task by verifying the implementation and promoting relevant learnings to the project memory.

Frequently Asked Questions about finishing-task

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I ensure task completion records and architectural decisions are preserved in project memory?

Task completion records and architectural decisions are preserved by formalizing task wrap-up through work validation and knowledge promotion to durable memory. This enforces a structured process ensuring project history is captured rather than lost when tasks finish.

What is the best way to formalize tracked task completion in a development workflow?

Formalizing tracked task completion requires enforcing predefined quality gates and explicit user authorization before finalizing task state. This validates factual work outcomes and updates durable documentation within task-based development workflows.

How do I promote project-wide learnings into durable knowledge management?

You promote project-wide learnings into knowledge management by identifying new architecture facts and decisions during task finalization, then writing them to persistent memory. This captures durable knowledge rather than abandoning records upon task finish.

Can I finalize task state without explicit user authorization?

No, finalizing task state requires explicit user authorization. The process enforces predefined quality gates to validate work outcomes, ensuring tasks finish with a factual, verified outcome rather than just being abandoned.

Do I need a task-based development workflow to use durable task completion?

Yes, durable task completion operates within the context of task-based development workflows. It requires this environment to validate work outcomes against predefined quality gates and preserve architectural decisions in project history.