Run any Skill in Manus with one click

full-feature-workflow

Stars1

Forks0

UpdatedFebruary 20, 2026 at 14:25

Execute a full feature workflow in order by chaining feature development, test writing, feature summaries, refactor analysis, selective refactor implementation, personal code review artifacts, and review-feedback triage when feedback is available. Use when the user wants an end-to-end structured delivery process.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

sunpar

sunpar/agentic_coding_tools

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

name	full-feature-workflow
description	Execute a full feature workflow in order by chaining feature development, test writing, feature summaries, refactor analysis, selective refactor implementation, personal code review artifacts, and review-feedback triage when feedback is available. Use when the user wants an end-to-end structured delivery process.

Full Feature Workflow

Execute these steps in order:

Determine git repository root.
Run the feature-dev workflow for the provided feature request.
Run the write-tests workflow for the implemented feature.
Run feature-summary and save to {git-root}/docs/feature-summary.md.
Run refactor-changes using feature context and save to {git-root}/docs/refactor.md.
Read {git-root}/docs/refactor.md, choose high-value low-risk refactors, and implement them.
Run feature-summary again and save to {git-root}/docs/feature-summary-2.md.
Run code-review-personal using updated context and save to {git-root}/docs/code-review-personal.md.
Run review-feedback-orchestrator using {git-root}/docs/code-review-personal.md from Step 8 as the primary review source (append PR comments or pasted notes if available). Save output to {git-root}/docs/review-feedback-resolution.md.

Rules

Preserve sequence; do not skip steps without explicit user approval.
Keep documentation artifacts concrete and file-backed.
Prefer minimal-risk implementation decisions while improving clarity and quality.
Step 9 should always start from {git-root}/docs/code-review-personal.md produced in Step 8; include external reviewer feedback as additional input when available.

More from this repository

same repository

gh-commit-pr-review

sunpar/agentic_coding_tools

Commit and publish local GitHub work with review requests. Use when the user wants Codex to commit staged changes, stage all changes only when nothing is staged, push the current branch, and open a GitHub pull request that tags @codex and @copilot for review.

2026-04-251

refactor-changes

sunpar/agentic_coding_tools

Analyze staged and unstaged git changes and refactor for readability, maintainability, and conciseness while preserving behavior. Use when the user asks to refactor recent changes, clean up work in progress, improve code quality, or review a diff for safe structural improvements.

2026-02-201

tasks-md-generator

sunpar/agentic_coding_tools

Generate implementation TASKS.md plans from one design document or from all feature documents in a directory.

2026-02-201

feature-dev

sunpar/agentic_coding_tools

Run a phased feature-development workflow: discovery, codebase exploration, clarifying questions, architecture options, implementation, quality review, and summary. Use when a user asks for end-to-end feature delivery with strong design rigor before coding.

2026-02-201

plan-to-doc-bundle

sunpar/agentic_coding_tools

Convert one planning document into PRD.md, USER_FLOW.md, BACKEND_ARCHITECTURE.md, FRONTEND_DESIGN.md, and TASKS.md in fixed deterministic order with a quality gate and traceability checks.

2026-02-201

deslop

sunpar/agentic_coding_tools

Remove AI-generated code slop from the current branch by auditing `git diff main...HEAD` and applying minimal cleanups. Use when a user asks to de-slop a PR/branch, make code look human-written, or remove over-defensive/verbose/generated patterns without changing behavior.

2026-02-201

name	full-feature-workflow
description	Execute a full feature workflow in order by chaining feature development, test writing, feature summaries, refactor analysis, selective refactor implementation, personal code review artifacts, and review-feedback triage when feedback is available. Use when the user wants an end-to-end structured delivery process.

Full Feature Workflow

Execute these steps in order:

Determine git repository root.
Run the feature-dev workflow for the provided feature request.
Run the write-tests workflow for the implemented feature.
Run feature-summary and save to {git-root}/docs/feature-summary.md.
Run refactor-changes using feature context and save to {git-root}/docs/refactor.md.
Read {git-root}/docs/refactor.md, choose high-value low-risk refactors, and implement them.
Run feature-summary again and save to {git-root}/docs/feature-summary-2.md.
Run code-review-personal using updated context and save to {git-root}/docs/code-review-personal.md.
Run review-feedback-orchestrator using {git-root}/docs/code-review-personal.md from Step 8 as the primary review source (append PR comments or pasted notes if available). Save output to {git-root}/docs/review-feedback-resolution.md.

Rules

Preserve sequence; do not skip steps without explicit user approval.
Keep documentation artifacts concrete and file-backed.
Prefer minimal-risk implementation decisions while improving clarity and quality.
Step 9 should always start from {git-root}/docs/code-review-personal.md produced in Step 8; include external reviewer feedback as additional input when available.