project-manager

End-to-end project orchestration from a prompt derives feature specs, phased plans, and delegated tasks into versioned markdown artifacts. It drives feature-driven development by converting your initial input into structured deliverables within a shared docs workspace.

Markdown-driven project management coordinates software workflows using centralized templates for feature specs and tasks. It enforces feature interviews, phased plan generation, and archival governance to maintain structured, versioned documentation throughout the project lifecycle.

Converting feature specs into delegated tasks involves phased plan generation that assigns clear roles to worker agents. The system tracks progress via completion sentinels and creates corrective tasks automatically upon failure, ensuring continuous workflow execution.

Markdown templates manage feature-driven development by storing generated specs, plans, and tasks in a shared, versioned workspace. This approach requires no external dependencies and relies entirely on centralized markdown files for project coordination and artifact archival.

Monitoring task completion and handling failure recovery relies on sentinel-based tracking and automated corrective task creation. When delegated tasks fail, the system generates corrective actions and archives finished work for audit, maintaining project continuity without manual intervention.

Sentinel-based completion is needed for workflow orchestration when tracking phased task delegation across worker agents. It provides automated progress verification, triggers failure recovery workflows, and ensures finished project artifacts are properly archived for governance.